Bandwidth part and uplink carrier switching

ABSTRACT

A wireless device receives first configuration parameters of a first bandwidth part and a second bandwidth part of a licensed cell; and second configuration parameters of a third bandwidth part and a fourth bandwidth part of an unlicensed cell. A first downlink control information indicating switching from the first bandwidth part to the second bandwidth part as an active bandwidth part is received. A second downlink control information indicating switching from the third bandwidth part to the fourth bandwidth part as an active bandwidth part is received. Based on the receiving the first downlink control information: the wireless device switches from the first bandwidth part to the second bandwidth part; and does not transmit a confirmation. Based on the receiving the second downlink control information, the wireless device switches from the third bandwidth part to the fourth bandwidth part; and transmits a confirmation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/736,842, filed Sep. 26, 2018, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per anaspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as peran aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stationsas per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals as per an aspect of an embodiment of the presentdisclosure.

FIG. 5B is a diagram of an example downlink channel mapping and exampledownlink physical signals as per an aspect of an embodiment of thepresent disclosure.

FIG. 6 is a diagram depicting an example frame structure as per anaspect of an embodiment of the present disclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDMsubcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS blocktransmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam managementprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of anembodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity asper an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per anaspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of anembodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 15 is a diagram of example RRC states as per an aspect of anembodiment of the present disclosure.

FIG. 16 is a diagram of example channel access priority class mapping toQCI as per an aspect of an embodiment of the present disclosure.

FIG. 17 is a diagram of example channel access priority class mapping tolisten-before-talk parameters as per an aspect of an embodiment of thepresent disclosure.

FIG. 18 is a diagram of example procedure as per an aspect of anembodiment of the present disclosure.

FIG. 19 is a diagram of example procedure as per an aspect of anembodiment of the present disclosure.

FIG. 20 is a diagram of example procedure as per an aspect of anembodiment of the present disclosure.

FIG. 21 is a diagram of example procedure as per an aspect of anembodiment of the present disclosure.

FIG. 22 is a diagram of example procedure as per an aspect of anembodiment of the present disclosure.

FIG. 23 is a diagram of example procedure as per an aspect of anembodiment of the present disclosure.

FIG. 24 is a diagram of example procedure as per an aspect of anembodiment of the present disclosure.

FIG. 25 is a diagram of example procedure as per an aspect of anembodiment of the present disclosure.

FIG. 26 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 27 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 28 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 29 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation of uplinkcarrier or bandwidth part switching. Embodiments of the technologydisclosed herein may be employed in the technical field of multicarriercommunication systems. More particularly, the embodiments of thetechnology disclosed herein may relate to uplink carrier or bandwidthpart switching in multicarrier communication systems.

The following Acronyms are used throughout the present disclosure:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BPSK Binary Phase Shift Keying

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CN Core Network

CP Cyclic Prefix

CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control CHannel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic CHannel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolved-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCID Logical Channel IDentifier

LTE Long Term Evolution

MAC Media Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node

NACK Negative Acknowledgement

NAS Non-Access Stratum

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-eNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NR PDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM Orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PMI Precoding Matrix Indicator

PRACH Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank Indicator

RLC Radio Link Control

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SC-FDMA Single Carrier-Frequency Division Multiple Access

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number

S-GW Serving GateWay

SI System Information

SIB System Information Block

SMF Session Management Function

SN Secondary Node

SpCell Special Cell

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSS Secondary Synchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance

TAG Timing Advance Group

TAI Tracking Area Identifier

TAT Time Alignment Timer

TB Transport Block

TC-RNTI Temporary Cell-Radio Network Temporary Identifier

TDD Time Division Duplex

TDMA Time Division Multiple Access

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared CHannel

UPF User Plane Function

UPGW User Plane Gateway

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CodeDivision Multiple Access (CDMA), Orthogonal Frequency Division MultipleAccess (OFDMA), Time Division Multiple Access (TDMA), Wavelettechnologies, and/or the like. Hybrid transmission mechanisms such asTDMA/CDMA, and OFDM/CDMA may also be employed. Various modulationschemes may be applied for signal transmission in the physical layer.Examples of modulation schemes include, but are not limited to: phase,amplitude, code, a combination of these, and/or the like. An exampleradio transmission method may implement Quadrature Amplitude Modulation(QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase ShiftKeying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, a RAN node may be a next generation Node B (gNB) (e.g.120A, 120B) providing New Radio (NR) user plane and control planeprotocol terminations towards a first wireless device (e.g. 110A). In anexample, a RAN node may be a next generation evolved Node B (ng-eNB)(e.g. 124A, 124B), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device (e.g. 110B). The first wireless device maycommunicate with a gNB over a Uu interface. The second wireless devicemay communicate with a ng-eNB over a Uu interface. In this disclosure,wireless device 110A and 110B are structurally similar to wirelessdevice 110. Base stations 120A and/or 120B may be structurally similarlyto base station 120. Base station 120 may comprise at least one of a gNB(e.g. 122A and/or 122B), ng-eNB (e.g. 124A and/or 124B), and or thelike.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of UEs inRRC_INACTIVE state, distribution function for Non-Access Stratum (NAS)messages, RAN sharing, and dual connectivity or tight interworkingbetween NR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may beinterconnected with each other by means of Xn interface. A gNB or anng-eNB may be connected by means of NG interfaces to 5G Core Network(5GC). In an example, 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may beconnected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g. non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer and/or warning message transmission, combinations thereof,and/or the like.

In an example, a UPF may host functions such as anchor point forintra-/inter-Radio Access Technology (RAT) mobility (when applicable),external PDU session point of interconnect to data network, packetrouting and forwarding, packet inspection and user plane part of policyrule enforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, QoS handling for user plane, e.g. packetfiltering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplinktraffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signalingtermination, NAS signaling security, Access Stratum (AS) securitycontrol, inter Core Network (CN) node signaling for mobility between3^(rd) Generation Partnership Project (3GPP) access networks, idle modeUE reachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (subscription and policies),support of network slicing and/or Session Management Function (SMF)selection.

FIG. 2A is an example user plane protocol stack, where Service DataAdaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers andPhysical (PHY) (e.g. 215 and 225) layer may be terminated in wirelessdevice (e.g. 110) and gNB (e.g. 120) on the network side. In an example,a PHY layer provides transport services to higher layers (e.g. MAC, RRC,etc.). In an example, services and functions of a MAC sublayer maycomprise mapping between logical channels and transport channels,multiplexing/demultiplexing of MAC Service Data Units (SDUs) belongingto one or different logical channels into/from Transport Blocks (TBs)delivered to/from the PHY layer, scheduling information reporting, errorcorrection through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between UEs by means of dynamic scheduling, priority handlingbetween logical channels of one UE by means of logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. In an example, mappingrestrictions in a logical channel prioritization may control whichnumerology and/or transmission timing a logical channel may use. In anexample, an RLC sublayer may supports transparent mode (TM),unacknowledged mode (UM) and acknowledged mode (AM) transmission modes.The RLC configuration may be per logical channel with no dependency onnumerologies and/or Transmission Time Interval (TTI) durations. In anexample, Automatic Repeat Request (ARQ) may operate on any of thenumerologies and/or TTI durations the logical channel is configuredwith. In an example, services and functions of the PDCP layer for theuser plane may comprise sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g. in case of split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. In an example, services andfunctions of SDAP may comprise mapping between a QoS flow and a dataradio bearer. In an example, services and functions of SDAP may comprisemapping Quality of Service Indicator (QFI) in DL and UL packets. In anexample, a protocol entity of SDAP may be configured for an individualPDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayersand PHY (e.g. 236 and 245) layer may be terminated in wireless device(e.g. 110) and gNB (e.g. 120) on a network side and perform service andfunctions described above. In an example, RRC (e.g. 232 and 241) may beterminated in a wireless device and a gNB on a network side. In anexample, services and functions of RRC may comprise broadcast of systeminformation related to AS and NAS, paging initiated by 5 GC or RAN,establishment, maintenance and release of an RRC connection between theUE and RAN, security functions including key management, establishment,configuration, maintenance and release of Signaling Radio Bearers (SRBs)and Data Radio Bearers (DRBs), mobility functions, QoS managementfunctions, UE measurement reporting and control of the reporting,detection of and recovery from radio link failure, and/or NAS messagetransfer to/from NAS from/to a UE. In an example, NAS control protocol(e.g. 231 and 251) may be terminated in the wireless device and AMF(e.g. 130) on a network side and may perform functions such asauthentication, mobility management between a UE and a AMF for 3GPPaccess and non-3GPP access, and session management between a UE and aSMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logicalchannels for a wireless device. A logical channel in the plurality oflogical channels may correspond to a radio bearer and the radio bearermay be associated with a QoS requirement. In an example, a base stationmay configure a logical channel to be mapped to one or moreTTIs/numerologies in a plurality of TTIs/numerologies. The wirelessdevice may receive a Downlink Control Information (DCI) via PhysicalDownlink Control CHannel (PDCCH) indicating an uplink grant. In anexample, the uplink grant may be for a first TTI/numerology and mayindicate uplink resources for transmission of a transport block. Thebase station may configure each logical channel in the plurality oflogical channels with one or more parameters to be used by a logicalchannel prioritization procedure at the MAC layer of the wirelessdevice. The one or more parameters may comprise priority, prioritizedbit rate, etc. A logical channel in the plurality of logical channelsmay correspond to one or more buffers comprising data associated withthe logical channel. The logical channel prioritization procedure mayallocate the uplink resources to one or more first logical channels inthe plurality of logical channels and/or one or more MAC ControlElements (CEs). The one or more first logical channels may be mapped tothe first TTI/numerology. The MAC layer at the wireless device maymultiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logicalchannel) in a MAC PDU (e.g., transport block). In an example, the MACPDU may comprise a MAC header comprising a plurality of MAC sub-headers.A MAC sub-header in the plurality of MAC sub-headers may correspond to aMAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/orone or more MAC SDUs. In an example, a MAC CE or a logical channel maybe configured with a Logical Channel IDentifier (LCID). In an example,LCID for a logical channel or a MAC CE may be fixed/pre-configured. Inan example, LCID for a logical channel or MAC CE may be configured forthe wireless device by the base station. The MAC sub-headercorresponding to a MAC CE or a MAC SDU may comprise LCID associated withthe MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/orimpact one or more processes (e.g., set values of one or more parametersof the one or more processes or start and/or stop one or more timers ofthe one or more processes) at the wireless device by employing one ormore MAC commands. The one or more MAC commands may comprise one or moreMAC control elements. In an example, the one or more processes maycomprise activation and/or deactivation of PDCP packet duplication forone or more radio bearers. The base station may transmit a MAC CEcomprising one or more fields, the values of the fields indicatingactivation and/or deactivation of PDCP duplication for the one or moreradio bearers. In an example, the one or more processes may compriseChannel State Information (CSI) transmission of on one or more cells.The base station may transmit one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells. Inan example, the one or more processes may comprise activation ordeactivation of one or more secondary cells. In an example, the basestation may transmit a MA CE indicating activation or deactivation ofone or more secondary cells. In an example, the base station maytransmit one or more MAC CEs indicating starting and/or stopping one ormore Discontinuous Reception (DRX) timers at the wireless device. In anexample, the base station may transmit one or more MAC CEs indicatingone or more timing advance values for one or more Timing Advance Groups(TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, andbase station 2, 120B) and a wireless device 110. A wireless device maybe called an UE. A base station may be called a NB, eNB, gNB, and/orng-eNB. In an example, a wireless device and/or a base station may actas a relay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g. a wireless modem, an antenna, a wiredmodem, and/or the like), at least one processor 321A, and at least oneset of program code instructions 323A stored in non-transitory memory322A and executable by the at least one processor 321A. The base station2, 120B, may comprise at least one communication interface 320B, atleast one processor 321B, and at least one set of program codeinstructions 323B stored in non-transitory memory 322B and executable bythe at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may comprise many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At Radio Resource Control (RRC)connection establishment/re-establishment/handover, one serving cell mayprovide the NAS (non-access stratum) mobility information (e.g. TrackingArea Identifier (TAI)). At RRC connection re-establishment/handover, oneserving cell may provide the security input. This cell may be referredto as the Primary Cell (PCell). In the downlink, a carrier correspondingto the PCell may be a DL Primary Component Carrier (PCC), while in theuplink, a carrier may be an UL PCC. Depending on wireless devicecapabilities, Secondary Cells (SCells) may be configured to formtogether with a PCell a set of serving cells. In a downlink, a carriercorresponding to an SCell may be a downlink secondary component carrier(DL SCC), while in an uplink, a carrier may be an uplink secondarycomponent carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to one cell. The cell ID or cell index may alsoidentify the downlink carrier or uplink carrier of the cell (dependingon the context it is used). In the disclosure, a cell ID may be equallyreferred to a carrier ID, and a cell index may be referred to a carrierindex. In an implementation, a physical cell ID or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted on a downlink carrier. A cell index may be determinedusing RRC messages. For example, when the disclosure refers to a firstphysical cell ID for a first downlink carrier, the disclosure may meanthe first physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.When the disclosure indicates that a first carrier is activated, thespecification may equally mean that a cell comprising the first carrieris activated.

A base station may transmit to a wireless device one or more messages(e.g. RRC messages) comprising a plurality of configuration parametersfor one or more cells. One or more cells may comprise at least oneprimary cell and at least one secondary cell. In an example, an RRCmessage may be broadcasted or unicasted to the wireless device. In anexample, configuration parameters may comprise common parameters anddedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). Another SI maybe transmitted via SystemInformationBlockType2. For a wireless device inan RRC_Connected state, dedicated RRC signaling may be employed for therequest and delivery of the other SI. For the wireless device in theRRC_Idle state and/or the RRC_Inactive state, the request may trigger arandom-access procedure.

A wireless device may report its radio access capability informationwhich may be static. A base station may request what capabilities for awireless device to report based on band information. When allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection witha network. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. When adding a new SCell,dedicated RRC signaling may be employed to send all required systeminformation of the SCell i.e. while in connected mode, wireless devicesmay not need to acquire broadcasted system information directly from theSCells.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells and cell groups). As part of the RRCconnection reconfiguration procedure, NAS dedicated information may betransferred from the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be to establish (or reestablish, resume) an RRC connection. an RRCconnection establishment procedure may comprise SRB1 establishment. TheRRC connection establishment procedure may be used to transfer theinitial NAS dedicated information/message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure after successful security activation. Ameasurement report message may be employed to transmit measurementresults.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g. a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 stored in non-transitory memory 315 and executable bythe at least one processor 314. The wireless device 110 may furthercomprise at least one of at least one speaker/microphone 311, at leastone keypad 312, at least one display/touchpad 313, at least one powersource 317, at least one global positioning system (GPS) chipset 318,and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding/processing, data processing, powercontrol, input/output processing, and/or any other functionality thatmay enable the wireless device 110, the base station 1 120A and/or thebase station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to thespeaker/microphone 311, the keypad 312, and/or the display/touchpad 313.The processor 314 may receive user input data from and/or provide useroutput data to the speaker/microphone 311, the keypad 312, and/or thedisplay/touchpad 313. The processor 314 in the wireless device 110 mayreceive power from the power source 317 and/or may be configured todistribute the power to the other components in the wireless device 110.The power source 317 may comprise at least one of one or more dry cellbatteries, solar cells, fuel cells, and the like. The processor 314 maybe connected to the GPS chipset 318. The GPS chipset 318 may beconfigured to provide geographic location information of the wirelessdevice 110.

The processor 314 of the wireless device 110 may further be connected toother peripherals 319, which may comprise one or more software and/orhardware modules that provide additional features and/orfunctionalities. For example, the peripherals 319 may comprise at leastone of an accelerometer, a satellite transceiver, a digital camera, auniversal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, and thelike.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110 via a wireless link 330A and/or a wireless link 330Brespectively. In an example, the communication interface 320A of thebase station 1, 120A, may communicate with the communication interface320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110 and/or thebase station 2 120B and the wireless device 110 may be configured tosend and receive transport blocks via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may employ at least one frequency carrier. Accordingto some of various aspects of embodiments, transceiver(s) may beemployed. A transceiver may be a device that comprises both atransmitter and a receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in thecommunication interface 310, 320A, 320B and the wireless link 330A, 330Bare illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A,FIG. 7B, FIG. 8, and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF,etc.) may comprise one or more communication interfaces, one or moreprocessors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers,switches, antennas, and/or the like) may comprise one or moreprocessors, and memory storing instructions that when executed by theone or more processors causes the node to perform certain processesand/or functions. Example embodiments may enable operation ofsingle-carrier and/or multi-carrier communications. Other exampleembodiments may comprise a non-transitory tangible computer readablemedia comprising instructions executable by one or more processors tocause operation of single-carrier and/or multi-carrier communications.Yet other example embodiments may comprise an article of manufacturethat comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a node to enable operation ofsingle-carrier and/or multi-carrier communications. The node may includeprocessors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and code stored in and/or incommunication with a memory device to implement connections, electronicdevice operations, protocol(s), protocol layers, communication drivers,device drivers, hardware operations, combinations thereof, and/or thelike.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 4A shows an example uplink transmitter forat least one physical channel A baseband signal representing a physicaluplink shared channel may perform one or more functions. The one or morefunctions may comprise at least one of: scrambling; modulation ofscrambled bits to generate complex-valued symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; transform precoding to generate complex-valued symbols;precoding of the complex-valued symbols; mapping of precodedcomplex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 4A. These functions are illustrated as examples andit is anticipated that other mechanisms may be implemented in variousembodiments.

An example structure for modulation and up-conversion to the carrierfrequency of the complex-valued SC-FDMA or CP-OFDM baseband signal foran antenna port and/or the complex-valued Physical Random Access CHannel(PRACH) baseband signal is shown in FIG. 4B. Filtering may be employedprior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. Thebaseband signal representing a downlink physical channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

In an example, a gNB may transmit a first symbol and a second symbol onan antenna port, to a wireless device. The wireless device may infer thechannel (e.g., fading gain, multipath delay, etc.) for conveying thesecond symbol on the antenna port, from the channel for conveying thefirst symbol on the antenna port. In an example, a first antenna portand a second antenna port may be quasi co-located if one or morelarge-scale properties of the channel over which a first symbol on thefirst antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals. FIG. 5B is a diagram of an example downlinkchannel mapping and a downlink physical signals. In an example, aphysical layer may provide one or more information transfer services toa MAC and/or one or more higher layers. For example, the physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and with what characteristics data are transferred over theradio interface.

In an example embodiment, a radio network may comprise one or moredownlink and/or uplink transport channels. For example, a diagram inFIG. 5A shows example uplink transport channels comprising Uplink-SharedCHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram inFIG. 5B shows example downlink transport channels comprisingDownlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, andBroadcast CHannel (BCH) 513. A transport channel may be mapped to one ormore corresponding physical channels. For example, UL-SCH 501 may bemapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may bemapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to PhysicalDownlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to PhysicalBroadcast CHannel (PBCH) 516.

There may be one or more physical channels without a correspondingtransport channel. The one or more physical channels may be employed forUplink Control Information (UCI) 509 and/or Downlink Control Information(DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 maycarry UCI 509 from a UE to a base station. For example, PhysicalDownlink Control CHannel (PDCCH) 515 may carry DCI 517 from a basestation to a UE. NR may support UCI 509 multiplexing in PUSCH 503 whenUCI 509 and PUSCH 503 transmissions may coincide in a slot at least inpart. The UCI 509 may comprise at least one of CSI, Acknowledgement(ACK)/Negative Acknowledgement (NACK), and/or scheduling request. TheDCI 517 on PDCCH 515 may indicate at least one of following: one or moredownlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to abase station. For example, the one or more RSs may be at least one ofDemodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/orSounding RS (SRS) 508. In downlink, a base station may transmit (e.g.,unicast, multicast, and/or broadcast) one or more RSs to a UE. Forexample, the one or more RSs may be at least one of PrimarySynchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521,CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a basestation for channel estimation, for example, for coherent demodulationof one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH504). For example, a UE may transmit a base station at least one uplinkDM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least oneuplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. In an example, a base station mayconfigure a UE with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to transmit at one or more symbols of a PUSCH and/or PUCCH. Abase station may semi-statistically configure a UE with a maximum numberof front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UEmay schedule a single-symbol DM-RS and/or double symbol DM-RS based on amaximum number of front-loaded DM-RS symbols, wherein a base station mayconfigure the UE with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, e.g., at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

In an example, whether uplink PT-RS 507 is present or not may depend ona RRC configuration. For example, a presence of uplink PT-RS may beUE-specifically configured. For example, a presence and/or a pattern ofuplink PT-RS 507 in a scheduled resource may be UE-specificallyconfigured by a combination of RRC signaling and/or association with oneor more parameters employed for other purposes (e.g., Modulation andCoding Scheme (MCS)) which may be indicated by DCI. When configured, adynamic presence of uplink PT-RS 507 may be associated with one or moreDCI parameters comprising at least MCS. A radio network may supportplurality of uplink PT-RS densities defined in time/frequency domain.When present, a frequency domain density may be associated with at leastone configuration of a scheduled bandwidth. A UE may assume a sameprecoding for a DMRS port and a PT-RS port. A number of PT-RS ports maybe fewer than a number of DM-RS ports in a scheduled resource. Forexample, uplink PT-RS 507 may be confined in the scheduledtime/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channelstate estimation to support uplink channel dependent scheduling and/orlink adaptation. For example, SRS 508 transmitted by a UE may allow fora base station to estimate an uplink channel state at one or moredifferent frequencies. A base station scheduler may employ an uplinkchannel state to assign one or more resource blocks of good quality foran uplink PUSCH transmission from a UE. A base station maysemi-statistically configure a UE with one or more SRS resource sets.For an SRS resource set, a base station may configure a UE with one ormore SRS resources. An SRS resource set applicability may be configuredby a higher layer (e.g., RRC) parameter. For example, when a higherlayer parameter indicates beam management, a SRS resource in each of oneor more SRS resource sets may be transmitted at a time instant. A UE maytransmit one or more SRS resources in different SRS resource setssimultaneously. A new radio network may support aperiodic, periodicand/or semi-persistent SRS transmissions. A UE may transmit SRSresources based on one or more trigger types, wherein the one or moretrigger types may comprise higher layer signaling (e.g., RRC) and/or oneor more DCI formats (e.g., at least one DCI format may be employed for aUE to select at least one of one or more configured SRS resource sets.An SRS trigger type 0 may refer to an SRS triggered based on a higherlayer signaling. An SRS trigger type 1 may refer to an SRS triggeredbased on one or more DCI formats. In an example, when PUSCH 503 and SRS508 are transmitted in a same slot, a UE may be configured to transmitSRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS506.

In an example, a base station may semi-statistically configure a UE withone or more SRS configuration parameters indicating at least one offollowing: a SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, afrequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one ormore OFDM symbols (e.g., 4 OFDM symbols numbered in increasing orderfrom 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprisePSS/SSS 521 and PBCH 516. In an example, in the frequency domain, anSS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240contiguous subcarriers with the subcarriers numbered in increasing orderfrom 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 mayoccupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may spanacross 3 OFDM symbols and 240 subcarriers. A UE may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, e.g., with respect to Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters. A UE may not assumequasi co-location for other SS/PBCH block transmissions. A periodicityof an SS/PBCH block may be configured by a radio network (e.g., by anRRC signaling) and one or more time locations where the SS/PBCH blockmay be sent may be determined by sub-carrier spacing. In an example, aUE may assume a band-specific sub-carrier spacing for an SS/PBCH blockunless a radio network has configured a UE to assume a differentsub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522.For example, a base station may semi-statistically configure and/orreconfigure a UE with periodic transmission of downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated ad/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation ofCSI-RS resource may be triggered dynamically. In an example, CSI-RSconfiguration may comprise one or more parameters indicating at least anumber of antenna ports. For example, a base station may configure a UEwith 32 ports. A base station may semi-statistically configure a UE withone or more CSI-RS resource sets. One or more CSI-RS resources may beallocated from one or more CSI-RS resource sets to one or more UEs. Forexample, a base station may semi-statistically configure one or moreparameters indicating CSI RS resource mapping, for example, time-domainlocation of one or more CSI-RS resources, a bandwidth of a CSI-RSresource, and/or a periodicity. In an example, a UE may be configured toemploy a same OFDM symbols for downlink CSI-RS 522 and control resourceset (coreset) when the downlink CSI-RS 522 and coreset are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are the outside of PRBs configured for coreset. In anexample, a UE may be configured to employ a same OFDM symbols fordownlink CSI-RS 522 and SSB/PBCH when the downlink CSI-RS 522 andSSB/PBCH are spatially quasi co-located and resource elements associatedwith the downlink CSI-RS 522 are the outside of PRBs configured forSSB/PBCH.

In an example, a UE may transmit one or more downlink DM-RSs 523 to abase station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variableand/or configurable DM-RS patterns for data demodulation. At least onedownlink DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-statisticallyconfigure a UE with a maximum number of front-loaded DM-RS symbols forPDSCH 514. For example, a DM-RS configuration may support one or moreDM-RS ports. For example, for single user-MIMO, a DM-RS configurationmay support at least 8 orthogonal downlink DM-RS ports. For example, formultiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlinkDM-RS ports. A radio network may support, e.g., at least for CP-OFDM, acommon DM-RS structure for DL and UL, wherein a DM-RS location, DM-RSpattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may dependon a RRC configuration. For example, a presence of downlink PT-RS 524may be UE-specifically configured. For example, a presence and/or apattern of downlink PT-RS 524 in a scheduled resource may beUE-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters employed for other purposes(e.g., MCS) which may be indicated by DCI. When configured, a dynamicpresence of downlink PT-RS 524 may be associated with one or more DCIparameters comprising at least MCS. A radio network may supportplurality of PT-RS densities defined in time/frequency domain. Whenpresent, a frequency domain density may be associated with at least oneconfiguration of a scheduled bandwidth. A UE may assume a same precodingfor a DMRS port and a PT-RS port. A number of PT-RS ports may be fewerthan a number of DM-RS ports in a scheduled resource. For example,downlink PT-RS 524 may be confined in the scheduled time/frequencyduration for a UE.

FIG. 6 is a diagram depicting an example frame structure for a carrieras per an aspect of an embodiment of the present disclosure. Amulticarrier OFDM communication system may include one or more carriers,for example, ranging from 1 to 32 carriers, in case of carrieraggregation, or ranging from 1 to 64 carriers, in case of dualconnectivity. Different radio frame structures may be supported (e.g.,for FDD and for TDD duplex mechanisms). FIG. 6 shows an example framestructure. Downlink and uplink transmissions may be organized into radioframes 601. In this example, radio frame duration is 10 ms. In thisexample, a 10 ms radio frame 601 may be divided into ten equally sizedsubframes 602 with 1 ms duration. Subframe(s) may comprise one or moreslots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 604.The number of OFDM symbols 604 in a slot 605 may depend on the cyclicprefix length. For example, a slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may contain downlink, uplink, or a downlink part and an uplinkpart and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as peran aspect of an embodiment of the present disclosure. In the example, agNB may communicate with a wireless device with a carrier with anexample channel bandwidth 700. Arrow(s) in the diagram may depict asubcarrier in a multicarrier OFDM system. The OFDM system may usetechnology such as OFDM technology, SC-FDMA technology, and/or the like.In an example, an arrow 701 shows a subcarrier transmitting informationsymbols. In an example, a subcarrier spacing 702, between two contiguoussubcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120KHz, 240 KHz etc. In an example, different subcarrier spacing maycorrespond to different transmission numerologies. In an example, atransmission numerology may comprise at least: a numerology index; avalue of subcarrier spacing; a type of cyclic prefix (CP). In anexample, a gNB may transmit to/receive from a UE on a number ofsubcarriers 703 in a carrier. In an example, a bandwidth occupied by anumber of subcarriers 703 (transmission bandwidth) may be smaller thanthe channel bandwidth 700 of a carrier, due to guard band 704 and 705.In an example, a guard band 704 and 705 may be used to reduceinterference to and from one or more neighbor carriers. A number ofsubcarriers (transmission bandwidth) in a carrier may depend on thechannel bandwidth of the carrier and the subcarrier spacing. Forexample, a transmission bandwidth, for a carrier with 20 MHz channelbandwidth and 15 KHz subcarrier spacing, may be in number of 1024subcarriers.

In an example, a gNB and a wireless device may communicate with multipleCCs when configured with CA. In an example, different component carriersmay have different bandwidth and/or subcarrier spacing, if CA issupported. In an example, a gNB may transmit a first type of service toa UE on a first component carrier. The gNB may transmit a second type ofservice to the UE on a second component carrier. Different type ofservices may have different service requirement (e.g., data rate,latency, reliability), which may be suitable for transmission viadifferent component carrier having different subcarrier spacing and/orbandwidth. FIG. 7B shows an example embodiment. A first componentcarrier may comprise a first number of subcarriers 706 with a firstsubcarrier spacing 709. A second component carrier may comprise a secondnumber of subcarriers 707 with a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 with athird subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. In an example, a carrier mayhave a transmission bandwidth 801. In an example, a resource grid may bein a structure of frequency domain 802 and time domain 803. In anexample, a resource grid may comprise a first number of OFDM symbols ina subframe and a second number of resource blocks, starting from acommon resource block indicated by higher-layer signaling (e.g. RRCsignaling), for a transmission numerology and a carrier. In an example,in a resource grid, a resource unit identified by a subcarrier index anda symbol index may be a resource element 805. In an example, a subframemay comprise a first number of OFDM symbols 807 depending on anumerology associated with a carrier. For example, when a subcarrierspacing of a numerology of a carrier is 15 KHz, a subframe may have 14OFDM symbols for a carrier. When a subcarrier spacing of a numerology is30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacingof a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. Inan example, a second number of resource blocks comprised in a resourcegrid of a carrier may depend on a bandwidth and a numerology of thecarrier.

As shown in FIG. 8, a resource block 806 may comprise 12 subcarriers. Inan example, multiple resource blocks may be grouped into a ResourceBlock Group (RBG) 804. In an example, a size of a RBG may depend on atleast one of: a RRC message indicating a RBG size configuration; a sizeof a carrier bandwidth; or a size of a bandwidth part of a carrier. Inan example, a carrier may comprise multiple bandwidth parts. A firstbandwidth part of a carrier may have different frequency location and/orbandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control informationcomprising a downlink or uplink resource block assignment to a wirelessdevice. A base station may transmit to or receive from, a wirelessdevice, data packets (e.g. transport blocks) scheduled and transmittedvia one or more resource blocks and one or more slots according toparameters in a downlink control information and/or RRC message(s). Inan example, a starting symbol relative to a first slot of the one ormore slots may be indicated to the wireless device. In an example, a gNBmay transmit to or receive from, a wireless device, data packetsscheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control informationcomprising a downlink assignment to a wireless device via one or morePDCCHs. The downlink assignment may comprise parameters indicating atleast modulation and coding format; resource allocation; and/or HARQinformation related to DL-SCH. In an example, a resource allocation maycomprise parameters of resource block allocation; and/or slotallocation. In an example, a gNB may dynamically allocate resources to awireless device via a Cell-Radio Network Temporary Identifier (C-RNTI)on one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible allocation when its downlink receptionis enabled. The wireless device may receive one or more downlink datapackage on one or more PDSCH scheduled by the one or more PDCCHs, whensuccessfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resourcesfor down link transmission to a wireless device. The gNB may transmitone or more RRC messages indicating a periodicity of the CS grant. ThegNB may transmit a DCI via a PDCCH addressed to a ConfiguredScheduling-RNTI (CS-RNTI) activating the CS resources. The DCI maycomprise parameters indicating that the downlink grant is a CS grant.The CS grant may be implicitly reused according to the periodicitydefined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control informationcomprising an uplink grant to a wireless device via one or more PDCCHs.The uplink grant may comprise parameters indicating at least modulationand coding format; resource allocation; and/or HARQ information relatedto UL-SCH. In an example, a resource allocation may comprise parametersof resource block allocation; and/or slot allocation. In an example, agNB may dynamically allocate resources to a wireless device via a C-RNTIon one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible resource allocation. The wirelessdevice may transmit one or more uplink data package via one or morePUSCH scheduled by the one or more PDCCHs, when successfully detectingthe one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink datatransmission to a wireless device. The gNB may transmit one or more RRCmessages indicating a periodicity of the CS grant. The gNB may transmita DCI via a PDCCH addressed to a CS-RNTI activating the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling viaPDCCH. The DCI may take a format in a plurality of formats. A DCI maycomprise downlink and/or uplink scheduling information (e.g., resourceallocation information, HARQ related parameters, MCS), request for CSI(e.g., aperiodic CQI reports), request for SRS, uplink power controlcommands for one or more cells, one or more timing information (e.g., TBtransmission/reception timing, HARQ feedback timing, etc.), etc. In anexample, a DCI may indicate an uplink grant comprising transmissionparameters for one or more transport blocks. In an example, a DCI mayindicate downlink assignment indicating parameters for receiving one ormore transport blocks. In an example, a DCI may be used by base stationto initiate a contention-free random access at the wireless device. Inan example, the base station may transmit a DCI comprising slot formatindicator (SFI) notifying a slot format. In an example, the base stationmay transmit a DCI comprising pre-emption indication notifying thePRB(s) and/or OFDM symbol(s) where a UE may assume no transmission isintended for the UE. In an example, the base station may transmit a DCIfor group power control of PUCCH or PUSCH or SRS. In an example, a DCImay correspond to an RNTI. In an example, the wireless device may obtainan RNTI in response to completing the initial access (e.g., C-RNTI). Inan example, the base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI(e.g., the wireless device may compute RA-RNTI based on resources usedfor transmission of a preamble). In an example, an RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). In an example, awireless device may monitor a group common search space which may beused by base station for transmitting DCIs that are intended for a groupof UEs. In an example, a group common DCI may correspond to an RNTIwhich is commonly configured for a group of UEs. In an example, awireless device may monitor a UE-specific search space. In an example, aUE specific DCI may correspond to an RNTI configured for the wirelessdevice.

A NR system may support a single beam operation and/or a multi-beamoperation. In a multi-beam operation, a base station may perform adownlink beam sweeping to provide coverage for common control channelsand/or downlink SS blocks, which may comprise at least a PSS, a SSS,and/or PBCH. A wireless device may measure quality of a beam pair linkusing one or more RSs. One or more SS blocks, or one or more CSI-RSresources, associated with a CSI-RS resource index (CRI), or one or moreDM-RSs of PBCH, may be used as RS for measuring quality of a beam pairlink. Quality of a beam pair link may be defined as a reference signalreceived power (RSRP) value, or a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. A RS resource and DM-RSs of a control channel may be calledQCLed when a channel characteristics from a transmission on an RS to awireless device, and that from a transmission on a control channel to awireless device, are similar or same under a configured criterion. In amulti-beam operation, a wireless device may perform an uplink beamsweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH onone or more beam pair links simultaneously depending on a capability ofa wireless device. This may increase robustness against beam pair linkblocking. A base station may transmit one or more messages to configurea wireless device to monitor PDCCH on one or more beam pair links indifferent PDCCH OFDM symbols. For example, a base station may transmithigher layer signaling (e.g. RRC signaling) or MAC CE comprisingparameters related to the Rx beam setting of a wireless device formonitoring PDCCH on one or more beam pair links. A base station maytransmit indication of spatial QCL assumption between an DL RS antennaport(s) (for example, cell-specific CSI-RS, or wireless device-specificCSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RSantenna port(s) for demodulation of DL control channel Signaling forbeam indication for a PDCCH may be MAC CE signaling, or RRC signaling,or DCI signaling, or specification-transparent and/or implicit method,and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. The base station may transmit DCI (e.g.downlink grants) comprising information indicating the RS antennaport(s). The information may indicate RS antenna port(s) which may beQCL-ed with the DM-RS antenna port(s). Different set of DM-RS antennaport(s) for a DL data channel may be indicated as QCL with different setof the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. For example, in a multi-beamoperation, a base station 120 may transmit SS blocks in multiple beams,together forming a SS burst 940. One or more SS blocks may betransmitted on one beam. If multiple SS bursts 940 are transmitted withmultiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation forestimating a beam quality of a links between a wireless device and abase station. A beam may be associated with a CSI-RS. For example, awireless device may, based on a RSRP measurement on CSI-RS, report abeam index, as indicated in a CRI for downlink beam selection, andassociated with a RSRP value of a beam. A CSI-RS may be transmitted on aCSI-RS resource including at least one of one or more antenna ports, oneor more time or frequency radio resources. A CSI-RS resource may beconfigured in a cell-specific way by common RRC signaling, or in awireless device-specific way by dedicated RRC signaling, and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be transmitted periodically, or using aperiodictransmission, or using a multi-shot or semi-persistent transmission. Forexample, in a periodic transmission in FIG. 9A, a base station 120 maytransmit configured CSI-RS resources 940 periodically using a configuredperiodicity in a time domain. In an aperiodic transmission, a configuredCSI-RS resource may be transmitted in a dedicated time slot. In amulti-shot or semi-persistent transmission, a configured CSI-RS resourcemay be transmitted within a configured period. Beams used for CSI-RStransmission may have different beam width than beams used for SS-blockstransmission.

FIG. 9B is an example of a beam management procedure in an example newradio network. A base station 120 and/or a wireless device 110 mayperform a downlink L1/L2 beam management procedure. One or more of thefollowing downlink L1/L2 beam management procedures may be performedwithin one or more wireless devices 110 and one or more base stations120. In an example, a P-1 procedure 910 may be used to enable thewireless device 110 to measure one or more Transmission (Tx) beamsassociated with the base station 120 to support a selection of a firstset of Tx beams associated with the base station 120 and a first set ofRx beam(s) associated with a wireless device 110. For beamforming at abase station 120, a base station 120 may sweep a set of different TXbeams. For beamforming at a wireless device 110, a wireless device 110may sweep a set of different Rx beams. In an example, a P-2 procedure920 may be used to enable a wireless device 110 to measure one or moreTx beams associated with a base station 120 to possibly change a firstset of Tx beams associated with a base station 120. A P-2 procedure 920may be performed on a possibly smaller set of beams for beam refinementthan in the P-1 procedure 910. A P-2 procedure 920 may be a special caseof a P-1 procedure 910. In an example, a P-3 procedure 930 may be usedto enable a wireless device 110 to measure at least one Tx beamassociated with a base station 120 to change a first set of Rx beamsassociated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reportsto a base station 120. In one or more beam management reports, awireless device 110 may indicate some beam pair quality parameters,comprising at least, one or more beam identifications; RSRP; PrecodingMatrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator(RI) of a subset of configured beams. Based on one or more beammanagement reports, a base station 120 may transmit to a wireless device110 a signal indicating that one or more beam pair links are one or moreserving beams. A base station 120 may transmit PDCCH and PDSCH for awireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a BandwidthAdaptation (BA). In an example, receive and/or transmit bandwidthsconfigured by an UE employing a BA may not be large. For example, areceive and/or transmit bandwidths may not be as large as a bandwidth ofa cell. Receive and/or transmit bandwidths may be adjustable. Forexample, a UE may change receive and/or transmit bandwidths, e.g., toshrink during period of low activity to save power. For example, a UEmay change a location of receive and/or transmit bandwidths in afrequency domain, e.g. to increase scheduling flexibility. For example,a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cellmay be referred to as a Bandwidth Part (BWP). A base station mayconfigure a UE with one or more BWPs to achieve a BA. For example, abase station may indicate, to a UE, which of the one or more(configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050)with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g. RRC layer)for a cell a set of one or more BWPs (e.g., at most four BWPs) forreceptions by the UE (DL BWP set) in a DL bandwidth by at least oneparameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs)for transmissions by a UE (UL BWP set) in an UL bandwidth by at leastone parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one ormore UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA),a base station may configure a UE at least with one or more DL BWPs(e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least oneof a location and number of contiguous PRBs, a subcarrier spacing, or acyclic prefix, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a UE is configured with a secondary carrier on a primary cell, the UEmay be configured with an initial BWP for random access procedure on asecondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that acenter frequency for a DL BWP may be same as a center frequency for a ULBWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPsor one or more UL BWPs, respectively, a base statin maysemi-statistically configure a UE for a cell with one or more parametersindicating at least one of following: a subcarrier spacing; a cyclicprefix; a number of contiguous PRBs; an index in the set of one or moreDL BWPs and/or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; a DCI detection to aPDSCH reception timing; a PDSCH reception to a HARQ-ACK transmissiontiming value; a DCI detection to a PUSCH transmission timing value; anoffset of a first PRB of a DL bandwidth or an UL bandwidth,respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell,a base station may configure a UE with one or more control resource setsfor at least one type of common search space and/or one UE-specificsearch space. For example, a base station may not configure a UE withouta common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station mayconfigure a UE with one or more resource sets for one or more PUCCHtransmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicatorfield value may indicate an active DL BWP, from a configured DL BWP set,for one or more DL receptions. If a DCI comprises a BWP indicator field,a BWP indicator field value may indicate an active UL BWP, from aconfigured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statisticallyconfigure a UE with a default DL BWP among configured DL BWPs. If a UEis not provided a default DL BWP, a default BWP may be an initial activeDL BWP.

In an example, a base station may configure a UE with a timer value fora PCell. For example, a UE may start a timer, referred to as BWPinactivity timer, when a UE detects a DCI indicating an active DL BWP,other than a default DL BWP, for a paired spectrum operation or when aUE detects a DCI indicating an active DL BWP or UL BWP, other than adefault DL BWP or UL BWP, for an unpaired spectrum operation. The UE mayincrement the timer by an interval of a first value (e.g., the firstvalue may be 1 millisecond or 0.5 milliseconds) if the UE does notdetect a DCI during the interval for a paired spectrum operation or foran unpaired spectrum operation. In an example, the timer may expire whenthe timer is equal to the timer value. A UE may switch to the default DLBWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of BWP inactivity timer(for example, the second BWP may be a default BWP). For example, FIG. 10is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2(1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a defaultBWP. BWP1 (1010) may be an initial active BWP. In an example, a UE mayswitch an active BWP from BWP1 1010 to BWP2 1020 in response to anexpiry of BWP inactivity timer. For example, a UE may switch an activeBWP from BWP2 1020 to BWP3 1030 in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in responseto receiving a DCI indicating an active BWP and/or in response to anexpiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a defaultDL BWP among configured DL BWPs and a timer value, UE procedures on asecondary cell may be same as on a primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DLBWP and a first active UL BWP on a secondary cell or carrier, a UE mayemploy an indicated DL BWP and an indicated UL BWP on a secondary cellas a respective first active DL BWP and first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity(e.g. dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A is an example diagram of a protocol structure of awireless device 110 (e.g. UE) with CA and/or multi connectivity as peran aspect of an embodiment. FIG. 11B is an example diagram of a protocolstructure of multiple base stations with CA and/or multi connectivity asper an aspect of an embodiment. The multiple base stations may comprisea master node, MN 1130 (e.g. a master node, a master base station, amaster gNB, a master eNB, and/or the like) and a secondary node, SN 1150(e.g. a secondary node, a secondary base station, a secondary gNB, asecondary eNB, and/or the like). A master node 1130 and a secondary node1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception/transmissionfunctions in an RRC connected state, may be configured to utilize radioresources provided by multiple schedulers of a multiple base stations.Multiple base stations may be inter-connected via a non-ideal or idealbackhaul (e.g. Xn interface, X2 interface, and/or the like). A basestation involved in multi connectivity for a certain wireless device mayperform at least one of two different roles: a base station may eitheract as a master base station or as a secondary base station. In multiconnectivity, a wireless device may be connected to one master basestation and one or more secondary base stations. In an example, a masterbase station (e.g. the MN 1130) may provide a master cell group (MCG)comprising a primary cell and/or one or more secondary cells for awireless device (e.g. the wireless device 110). A secondary base station(e.g. the SN 1150) may provide a secondary cell group (SCG) comprising aprimary secondary cell (PSCell) and/or one or more secondary cells for awireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a beareremploys may depend on how a bearer is setup. In an example, threedifferent type of bearer setup options may be supported: an MCG bearer,an SCG bearer, and/or a split bearer. A wireless device mayreceive/transmit packets of an MCG bearer via one or more cells of theMCG, and/or may receive/transmits packets of an SCG bearer via one ormore cells of an SCG. Multi-connectivity may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not beconfigured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmitand/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer viaan SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one ofa master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and oneof a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119);and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), aPDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and aMAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondarybase station (e.g. SN 1150) may transmit/receive: packets of an MCGbearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and amaster node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via amaster or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), asecondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and asecondary node MAC layer (e.g. SN MAC 1148); packets of a split bearervia a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), amaster or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SNRLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g.MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities: one MAC entity (e.g. MN MAC 1118) for a master base station,and other MAC entities (e.g. SN MAC 1119) for a secondary base station.In multi-connectivity, a configured set of serving cells for a wirelessdevice may comprise two subsets: an MCG comprising serving cells of amaster base station, and SCGs comprising serving cells of a secondarybase station. For an SCG, one or more of following configurations may beapplied: at least one cell of an SCG has a configured UL CC and at leastone cell of a SCG, named as primary secondary cell (PSCell, PCell ofSCG, or sometimes called PCell), is configured with PUCCH resources;when an SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or a number of NR RLC retransmissions hasbeen reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, forsplit bearer, a DL data transfer over a master base station may bemaintained; an NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer; PCell and/or PSCell may not be de-activated; PSCellmay be changed with a SCG change procedure (e.g. with security keychange and a RACH procedure); and/or a bearer type change between asplit bearer and a SCG bearer or simultaneous configuration of a SCG anda split bearer may or may not supported.

With respect to interaction between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be applied: a master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice; a master base station may (e.g. based on received measurementreports, traffic conditions, and/or bearer types) may decide to requesta secondary base station to provide additional resources (e.g. servingcells) for a wireless device; upon receiving a request from a masterbase station, a secondary base station may create/modify a containerthat may result in configuration of additional serving cells for awireless device (or decide that the secondary base station has noresource available to do so); for a UE capability coordination, a masterbase station may provide (a part of) an AS configuration and UEcapabilities to a secondary base station; a master base station and asecondary base station may exchange information about a UE configurationby employing of RRC containers (inter-node messages) carried via Xnmessages; a secondary base station may initiate a reconfiguration of thesecondary base station existing serving cells (e.g. PUCCH towards thesecondary base station); a secondary base station may decide which cellis a PSCell within a SCG; a master base station may or may not changecontent of RRC configurations provided by a secondary base station; incase of a SCG addition and/or a SCG SCell addition, a master basestation may provide recent (or the latest) measurement results for SCGcell(s); a master base station and secondary base stations may receiveinformation of SFN and/or subframe offset of each other from OAM and/orvia an Xn interface, (e.g. for a purpose of DRX alignment and/oridentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signaling may be used for sending requiredsystem information of a cell as for CA, except for a SFN acquired from aMIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival during RRC_CONNECTED when UL synchronization status isnon-synchronized, transition from RRC_Inactive, and/or request for othersystem information. For example, a PDCCH order, a MAC entity, and/or abeam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least oneof a contention based random access procedure and a contention freerandom access procedure. For example, a contention based random accessprocedure may comprise, one or more Msg 1 1220 transmissions, one ormore Msg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. For example, a contention free random accessprocedure may comprise one or more Msg 1 1220 transmissions and one ormore Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, orbroadcast), to a UE, a RACH configuration 1210 via one or more beams.The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: available set of PRACH resourcesfor a transmission of a random access preamble, initial preamble power(e.g., random access preamble initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., random access preamble powerramping step), random access preamble index, a maximum number ofpreamble transmission, preamble group A and group B, a threshold (e.g.,message size) to determine the groups of random access preambles, a setof one or more random access preambles for system information requestand corresponding PRACH resource(s), if any, a set of one or more randomaccess preambles for beam failure recovery request and correspondingPRACH resource(s), if any, a time window to monitor RA response(s), atime window to monitor response(s) on beam failure recovery request,and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of arandom access preamble. For a contention based random access procedure,a UE may select a SS block with a RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a UE may select one or morerandom access preambles from a group A or a group B depending on apotential Msg3 1240 size. If a random access preambles group B does notexist, a UE may select the one or more random access preambles from agroup A. A UE may select a random access preamble index randomly (e.g.with equal probability or a normal distribution) from one or more randomaccess preambles associated with a selected group. If a base stationsemi-statistically configures a UE with an association between randomaccess preambles and SS blocks, the UE may select a random accesspreamble index randomly with equal probability from one or more randomaccess preambles associated with a selected SS block and a selectedgroup.

For example, a UE may initiate a contention free random access procedurebased on a beam failure indication from a lower layer. For example, abase station may semi-statistically configure a UE with one or morecontention free PRACH resources for beam failure recovery requestassociated with at least one of SS blocks and/or CSI-RSs. If at leastone of SS blocks with a RSRP above a first RSRP threshold amongstassociated SS blocks or at least one of CSI-RSs with a RSRP above asecond RSRP threshold amongst associated CSI-RSs is available, a UE mayselect a random access preamble index corresponding to a selected SSblock or CSI-RS from a set of one or more random access preambles forbeam failure recovery request.

For example, a UE may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. If a base station does not configure a UE with at least onecontention free PRACH resource associated with SS blocks or CSI-RS, theUE may select a random access preamble index. If a base stationconfigures a UE with one or more contention free PRACH resourcesassociated with SS blocks and at least one SS block with a RSRP above afirst RSRP threshold amongst associated SS blocks is available, the UEmay select the at least one SS block and select a random access preamblecorresponding to the at least one SS block. If a base station configuresa UE with one or more contention free PRACH resources associated withCSI-RSs and at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available, the UE may selectthe at least one CSI-RS and select a random access preamblecorresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting theselected random access preamble. For example, if a UE selects an SSblock and is configured with an association between one or more PRACHoccasions and one or more SS blocks, the UE may determine an PRACHoccasion from one or more PRACH occasions corresponding to a selected SSblock. For example, if a UE selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs,the UE may determine a PRACH occasion from one or more PRACH occasionscorresponding to a selected CSI-RS. A UE may transmit, to a basestation, a selected random access preamble via a selected PRACHoccasions. A UE may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. A UE may determine a RA-RNTIassociated with a selected PRACH occasions in which a selected randomaccess preamble is transmitted. For example, a UE may not determine aRA-RNTI for a beam failure recovery request. A UE may determine anRA-RNTI at least based on an index of a first OFDM symbol and an indexof a first slot of a selected PRACH occasions, and/or an uplink carrierindex for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random accessresponse, Msg 2 1230. A UE may start a time window (e.g., ra-ResponseWindow) to monitor a random access response. For beam failure recoveryrequest, a base station may configure a UE with a different time window(e.g., bfr-ResponseWindow) to monitor response on beam failure recoveryrequest. For example, a UE may start a time window (e.g.,ra-ResponseWindow or bfr-ResponseWindow) at a start of a first PDCCHoccasion after a fixed duration of one or more symbols from an end of apreamble transmission. If a UE transmits multiple preambles, the UE maystart a time window at a start of a first PDCCH occasion after a fixedduration of one or more symbols from an end of a first preambletransmission. A UE may monitor a PDCCH of a cell for at least one randomaccess response identified by a RA-RNTI or for at least one response tobeam failure recovery request identified by a C-RNTI while a timer for atime window is running

In an example, a UE may consider a reception of random access responsesuccessful if at least one random access response comprises a randomaccess preamble identifier corresponding to a random access preambletransmitted by the UE. A UE may consider the contention free randomaccess procedure successfully completed if a reception of random accessresponse is successful. If a contention free random access procedure istriggered for a beam failure recovery request, a UE may consider acontention free random access procedure successfully complete if a PDCCHtransmission is addressed to a C-RNTI. In an example, if at least onerandom access response comprises a random access preamble identifier, aUE may consider the random access procedure successfully completed andmay indicate a reception of an acknowledgement for a system informationrequest to upper layers. If a UE has signaled multiple preambletransmissions, the UE may stop transmitting remaining preambles (if any)in response to a successful reception of a corresponding random accessresponse.

In an example, a UE may perform one or more Msg 3 1240 transmissions inresponse to a successful reception of random access response (e.g., fora contention based random access procedure). A UE may adjust an uplinktransmission timing based on a timing advanced command indicated by arandom access response and may transmit one or more transport blocksbased on an uplink grant indicated by a random access response.Subcarrier spacing for PUSCH transmission for Msg3 1240 may be providedby at least one higher layer (e.g. RRC) parameter. A UE may transmit arandom access preamble via PRACH and Msg3 1240 via PUSCH on a same cell.A base station may indicate an UL BWP for a PUSCH transmission of Msg31240 via system information block. A UE may employ HARQ for aretransmission of Msg 3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting asame preamble to a base station and receive, from the base station, asame random access response comprising an identity (e.g., TC-RNTI).Contention resolution 1250 may ensure that a UE does not incorrectly usean identity of another UE. For example, contention resolution 1250 maybe based on C-RNTI on PDCCH or a UE contention resolution identity onDL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UEmay perform contention resolution 1250 based on a reception of a PDCCHtransmission that is addressed to the C-RNTI. In response to detectionof a C-RNTI on a PDCCH, a UE may consider contention resolution 1250successful and may consider a random access procedure successfullycompleted. If a UE has no valid C-RNTI, a contention resolution may beaddressed by employing a TC-RNTI. For example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises a UE contention resolutionidentity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UEmay consider the contention resolution 1250 successful and may considerthe random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of anembodiment. In an example, a wireless device may be configured tooperate in a multi-connectivity mode. A wireless device in RRC_CONNECTEDwith multiple RX/TX may be configured to utilize radio resourcesprovided by multiple schedulers located in a plurality of base stations.The plurality of base stations may be connected via a non-ideal or idealbackhaul over the Xn interface. In an example, a base station in aplurality of base stations may act as a master base station or as asecondary base station. A wireless device may be connected to one masterbase station and one or more secondary base stations. A wireless devicemay be configured with multiple MAC entities, e.g. one MAC entity formaster base station, and one or more other MAC entities for secondarybase station(s). In an example, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 illustrates an examplestructure for MAC entities when MCG and SCG are configured for awireless device.

In an example, at least one cell in a SCG may have a configured UL CC,wherein a cell of at least one cell may be called PSCell or PCell ofSCG, or sometimes may be simply called PCell. A PSCell may be configuredwith PUCCH resources. In an example, when a SCG is configured, there maybe at least one SCG bearer or one split bearer. In an example, upondetection of a physical layer problem or a random access problem on aPSCell, or upon reaching a number of RLC retransmissions associated withthe SCG, or upon detection of an access problem on a PSCell during a SCGaddition or a SCG change: an RRC connection re-establishment proceduremay not be triggered, UL transmissions towards cells of an SCG may bestopped, a master base station may be informed by a UE of a SCG failuretype and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transferand radio resource allocation to upper layers (e.g. 1310 or 1320). A MACsublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360).A MAC sublayer may provide data transfer services on logical channels.To accommodate different kinds of data transfer services, multiple typesof logical channels may be defined. A logical channel may supporttransfer of a particular type of information. A logical channel type maybe defined by what type of information (e.g., control or data) istransferred. For example, BCCH, PCCH, CCCH and DCCH may be controlchannels and DTCH may be a traffic channel. In an example, a first MACentity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCHand MAC control elements. In an example, a second MAC entity (e.g. 1320)may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,signaling of scheduling request or measurements (e.g. CQI). In anexample, in dual connectivity, two MAC entities may be configured for awireless device: one for MCG and one for SCG. A MAC entity of wirelessdevice may handle a plurality of transport channels. In an example, afirst MAC entity may handle first transport channels comprising a PCCHof MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one ormore first UL-SCHs of MCG and one or more first RACHs of MCG. In anexample, a second MAC entity may handle second transport channelscomprising a second BCH of SCG, one or more second DL-SCHs of SCG, oneor more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells,there may be multiple DL-SCHs and there may be multiple UL-SCHs as wellas multiple RACHs per MAC entity. In an example, there may be one DL-SCHand UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero orone UL-SCH and zero or one RACH for an SCell. A DL-SCH may supportreceptions using different numerologies and/or TTI duration within a MACentity. A UL-SCH may also support transmissions using differentnumerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and maycontrol these functions with a control (e.g. 1355 or 1365) element.Functions performed by a MAC entity may comprise mapping between logicalchannels and transport channels (e.g., in uplink or downlink),multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TB) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g. 1352 or 1362) of MAC SDUs to one or different logical channelsfrom transport blocks (TB) delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink or downlink(e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or1361). A MAC entity may handle a random access process (e.g. 1354 or1364).

FIG. 14 is an example diagram of a RAN architecture comprising one ormore base stations. In an example, a protocol stack (e.g. RRC, SDAP,PDCP, RLC, MAC, and PHY) may be supported at a node. A base station(e.g. 120A or 120B) may comprise a base station central unit (CU) (e.g.gNB-CU 1420A or 1420B) and at least one base station distributed unit(DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functional splitis configured. Upper protocol layers of a base station may be located ina base station CU, and lower layers of the base station may be locatedin the base station DUs. An F1 interface (e.g. CU-DU interface)connecting a base station CU and base station DUs may be an ideal ornon-ideal backhaul. F1-C may provide a control plane connection over anF1 interface, and F1-U may provide a user plane connection over the F1interface. In an example, an Xn interface may be configured between basestation CUs.

In an example, a base station CU may comprise an RRC function, an SDAPlayer, and a PDCP layer, and base station DUs may comprise an RLC layer,a MAC layer, and a PHY layer. In an example, various functional splitoptions between a base station CU and base station DUs may be possibleby locating different combinations of upper protocol layers (RANfunctions) in a base station CU and different combinations of lowerprotocol layers (RAN functions) in base station DUs. A functional splitmay support flexibility to move protocol layers between a base stationCU and base station DUs depending on service requirements and/or networkenvironments.

In an example, functional split options may be configured per basestation, per base station CU, per base station DU, per UE, per bearer,per slice, or with other granularities. In per base station CU split, abase station CU may have a fixed split option, and base station DUs maybe configured to match a split option of a base station CU. In per basestation DU split, a base station DU may be configured with a differentsplit option, and a base station CU may provide different split optionsfor different base station DUs. In per UE split, a base station (basestation CU and at least one base station DUs) may provide differentsplit options for different wireless devices. In per bearer split,different split options may be utilized for different bearers. In perslice splice, different split options may be applied for differentslices.

FIG. 15 is an example diagram showing RRC state transitions of awireless device. In an example, a wireless device may be in at least oneRRC state among an RRC connected state (e.g. RRC Connected 1530,RRC_Connected), an RRC idle state (e.g. RRC Idle 1510, RRC_Idle), and/oran RRC inactive state (e.g. RRC Inactive 1520, RRC_Inactive). In anexample, in an RRC connected state, a wireless device may have at leastone RRC connection with at least one base station (e.g. gNB and/or eNB),which may have a UE context of the wireless device. A UE context (e.g. awireless device context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an example, in an RRC idle state, a wireless device may nothave an RRC connection with a base station, and a UE context of awireless device may not be stored in a base station. In an example, inan RRC inactive state, a wireless device may not have an RRC connectionwith a base station. A UE context of a wireless device may be stored ina base station, which may be called as an anchor base station (e.g. lastserving base station).

In an example, a wireless device may transition a UE RRC state betweenan RRC idle state and an RRC connected state in both ways (e.g.connection release 1540 or connection establishment 1550; or connectionreestablishment) and/or between an RRC inactive state and an RRCconnected state in both ways (e.g. connection inactivation 1570 orconnection resume 1580). In an example, a wireless device may transitionits RRC state from an RRC inactive state to an RRC idle state (e.g.connection release 1560).

In an example, an anchor base station may be a base station that maykeep a UE context (a wireless device context) of a wireless device atleast during a time period that a wireless device stays in a RANnotification area (RNA) of an anchor base station, and/or that awireless device stays in an RRC inactive state. In an example, an anchorbase station may be a base station that a wireless device in an RRCinactive state was lastly connected to in a latest RRC connected stateor that a wireless device lastly performed an RNA update procedure in.In an example, an RNA may comprise one or more cells operated by one ormore base stations. In an example, a base station may belong to one ormore RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from anRRC connected state to an RRC inactive state in a base station. Awireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RANpaging message) to base stations of an RNA to reach to a wireless devicein an RRC inactive state, and/or the base stations receiving the messagefrom the anchor base station may broadcast and/or multicast anothermessage (e.g. paging message) to wireless devices in their coveragearea, cell coverage area, and/or beam coverage area associated with theRNA through an air interface.

In an example, when a wireless device in an RRC inactive state movesinto a new RNA, the wireless device may perform an RNA update (RNAU)procedure, which may comprise a random access procedure by the wirelessdevice and/or a UE context retrieve procedure. A UE context retrieve maycomprise: receiving, by a base station from a wireless device, a randomaccess preamble; and fetching, by a base station, a UE context of thewireless device from an old anchor base station. Fetching may comprise:sending a retrieve UE context request message comprising a resumeidentifier to the old anchor base station and receiving a retrieve UEcontext response message comprising the UE context of the wirelessdevice from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state mayselect a cell to camp on based on at least a on measurement results forone or more cells, a cell where a wireless device may monitor an RNApaging message and/or a core network paging message from a base station.In an example, a wireless device in an RRC inactive state may select acell to perform a random access procedure to resume an RRC connectionand/or to transmit one or more packets to a base station (e.g. to anetwork). In an example, if a cell selected belongs to a different RNAfrom an RNA for a wireless device in an RRC inactive state, the wirelessdevice may initiate a random access procedure to perform an RNA updateprocedure. In an example, if a wireless device in an RRC inactive statehas one or more packets, in a buffer, to transmit to a network, thewireless device may initiate a random access procedure to transmit oneor more packets to a base station of a cell that the wireless deviceselects. A random access procedure may be performed with two messages(e.g. 2 stage random access) and/or four messages (e.g. 4 stage randomaccess) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplinkpackets from a wireless device in an RRC inactive state may fetch a UEcontext of a wireless device by transmitting a retrieve UE contextrequest message for the wireless device to an anchor base station of thewireless device based on at least one of an AS context identifier, anRNA identifier, a base station identifier, a resume identifier, and/or acell identifier received from the wireless device. In response tofetching a UE context, a base station may transmit a path switch requestfor a wireless device to a core network entity (e.g. AMF, MME, and/orthe like). A core network entity may update a downlink tunnel endpointidentifier for one or more bearers established for the wireless devicebetween a user plane core network entity (e.g. UPF, S-GW, and/or thelike) and a RAN node (e.g. the base station), e.g. changing a downlinktunnel endpoint identifier from an address of the anchor base station toan address of the base station.

A gNB may communicate with a wireless device via a wireless networkemploying one or more new radio technologies. The one or more radiotechnologies may comprise at least one of: multiple technologies relatedto physical layer; multiple technologies related to medium accesscontrol layer; and/or multiple technologies related to radio resourcecontrol layer. Example embodiments of enhancing the one or more radiotechnologies may improve performance of a wireless network. Exampleembodiments may increase the system throughput, or data rate oftransmission. Example embodiments may reduce battery consumption of awireless device. Example embodiments may improve latency of datatransmission between a gNB and a wireless device. Example embodimentsmay improve network coverage of a wireless network. Example embodimentsmay improve transmission efficiency of a wireless network.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. Thisrequires not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum is therefore needed for cellularoperators to meet the increasing demand Considering user expectations ofhigh data rates along with seamless mobility, it is beneficial that morespectrum be made available for deploying macro cells as well as smallcells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, can be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA offers an alternative for operators to make use of unlicensedspectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAutilizes at least energy detection to determine the presence or absenceof other signals on a channel in order to determine if a channel isoccupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by UEs; time & frequency synchronizationof UEs.

In an example embodiment, DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the eNBtransmissions can start only at the subframe boundary. LAA may supporttransmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

LBT procedure may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. While nodes may follow such regulatoryrequirements, a node may optionally use a lower threshold for energydetection than that specified by regulatory requirements. In an example,LAA may employ a mechanism to adaptively change the energy detectionthreshold, e.g., LAA may employ a mechanism to adaptively lower theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. In anexample Category 4 LBT mechanism or other type of LBT mechanisms may beimplemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (e.g. LBT without randomback-off) may be implemented. The duration of time that the channel issensed to be idle before the transmitting entity transmits may bedeterministic. In an example, Category 3 (e.g. LBT with random back-offwith a contention window of fixed size) may be implemented. The LBTprocedure may have the following procedure as one of its components. Thetransmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by theminimum and maximum value of N. The size of the contention window may befixed. The random number N may be employed in the LBT procedure todetermine the duration of time that the channel is sensed to be idlebefore the transmitting entity transmits on the channel. In an example,Category 4 (e.g. LBT with random back-off with a contention window ofvariable size) may be implemented. The transmitting entity may draw arandom number N within a contention window. The size of contentionwindow may be specified by the minimum and maximum value of N. Thetransmitting entity may vary the size of the contention window whendrawing the random number N. The random number N is used in the LBTprocedure to determine the duration of time that the channel is sensedto be idle before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the UE. The UL LBT scheme may be differentfrom the DL LBT scheme (e.g. by using different LBT mechanisms orparameters) for example, since the LAA UL is based on scheduled accesswhich affects a UE's channel contention opportunities. Otherconsiderations motivating a different UL LBT scheme include, but are notlimited to, multiplexing of multiple UEs in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from aUE perspective may be a continuous transmission from a UE with notransmission immediately before or after from the same UE on the sameCC. In an example, UL transmission burst is defined from a UEperspective. In an example, an UL transmission burst may be defined froman eNB perspective. In an example, in case of an eNB operating DL+UL LAAover the same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. For example, an instant in time may be part ofa DL transmission burst or an UL transmission burst.

In an example, single and multiple DL to UL and UL to DL switchingwithin a shared gNB COT may be supported. Example LBT requirements tosupport single or multiple switching points, may include: for gap ofless than 16 us: no-LBT may be used; for gap of above 16 us but does notexceed 25 us: one-shot LBT may be used; for single switching point, forthe gap from DL transmission to UL transmission exceeds 25 us: one-shotLBT may be used; for multiple switching points, for the gap from DLtransmission to UL transmission exceeds 25 us, one-shot LBT may be used.

In an example, a signal that facilitates its detection with lowcomplexity may be useful for UE power saving; Improved coexistence;Spatial reuse at least within the same operator network, Serving celltransmission burst acquisition, etc.

In an example, operation of new radio on unlicensed bands (NR-U) mayemploy a signal that contains at least SS/PBCH block burst settransmission. In an example, other channels and signals may betransmitted together as part of the signal. The design of this signalmay consider there are no gaps within the time span the signal istransmitted at least within a beam. In an example, gaps may be neededfor beam switching. In an example, the occupied channel bandwidth may besatisfied.

In an example, a block-interlaced based PUSCH may be employed. In anexample, the same interlace structure for PUCCH and PUSCH may be used.In an example, interlaced based PRACH may be used.

In an example, initial active DL/UL BWP may be approximately 20 MHz for5 GHz band. In an example, initial active DL/UL BWP may be approximately20 MHz for 6 GHz band if similar channelization as 5 GHz band is usedfor 6 GHz band.

In an example, HARQ A/N for the corresponding data may be transmitted inthe same shared COT. In some examples, the HARQ A/N may be transmittedin a separate COT from the one the corresponding data was transmitted.

In an example, when UL HARQ feedback is transmitted on unlicensed band,NR-U may consider mechanisms to support flexible triggering andmultiplexing of HARQ feedback for one or more DL HARQ processes.

In an example, the dependencies of HARQ process information to thetiming may be removed. In an example, UCI on PUSCH may carry HARQprocess ID, NDI, RVID. In an example, Downlink Feedback Information(DFI) may be used for transmission of HARQ feedback for configuredgrant.

In an example, both CBRA and CFRA may be supported on NR-U SpCell andCFRA may be supported on NR-U SCells. In an example, RAR may betransmitted via SpCell. In an example, a predefined HARQ process ID forRAR.

In an example, carrier aggregation between licensed band NR (PCell) andNR-U (SCell) may be supported. In an example, NR-U SCell may have bothDL and UL, or DL-only. In an example, dual connectivity between licensedband LTE (PCell) and NR-U (PSCell) may be supported. In an example,Stand-alone NR-U where all carriers are in unlicensed spectrum may besupported. In an example, an NR cell with DL in unlicensed band and ULin licensed band may be supported. In an example, dual connectivitybetween licensed band NR (PCell) and NR-U (PSCell) may be supported.

In an example, if absence of Wi-Fi cannot be guaranteed (e.g. byregulation) in a band (e.g., sub-7 GHz) where NR-U is operating, theNR-U operating bandwidth may be an integer multiple of 20 MHz. In anexample, at least for band where absence of Wi-Fi cannot be guaranteed(e.g. by regulation), LBT can be performed in units of 20 MHz. In anexample, receiver assisted LBT (e.g., RTS/CTS type mechanism) and/oron-demand receiver assisted LBT (e.g., for example receiver assisted LBTenabled only when needed) may be employed. In an example, techniques toenhance spatial reuse may be used. In an example, preamble detection maybe used.

In an example, with scheduled PUSCH transmissions on an unlicensedcarrier, the network first needs to gain access to the channel totransmit PDCCH and then the UE needs to perform LBT again prior totransmitting on the resource. Such procedure tends to increase latencyespecially when the channel is loaded. In an example, a mechanism ofautonomous uplink transmission may be used. In an example, a UE may bepre-allocated a resource for transmission similar to UL SPS and performsLBT prior to using the resource. In an example, autonomous uplink may bebased on the Configured Grant functionality (e.g., Type 1 and/or Type2).

In an example, the HARQ process identity may be transmitted by the UE(e.g., as UCI). This may enable a UE to use the first availabletransmission opportunity irrespective of the HARQ process. In anexample, UCI on PUSCH may be used to carry HARQ process ID, NDI andRVID.

For unlicensed band, UL dynamic grant scheduled transmission mayincrease the delay and transmission failure possibility due to at leasttwo LBTs of UE and gNB. Pre-configured grant such as configured grant inNR may be used for NR-U, which may decrease the number of LBTs performedand control signaling overhead.

In an example, in a Type 1 configured grant, an uplink grant is providedby RRC, and stored as configured uplink grant. In an example, in Type 2configured grant, an uplink grant is provided by PDCCH, and stored orcleared as configured uplink grant based on L1 signalling indicatingconfigured grant activation or deactivation.

In an example, there may not be a dependency between HARQ processinformation to the timing. In an example, UCI on PUSCH may carry HARQprocess ID, NDI, RVID, etc. In an example, UE may autonomously selectone HARQ process ID which is informed to gNB by UCI.

In an example, a UE may perform non-adaptive retransmission with theconfigured uplink grant. When dynamic grant for configured grantretransmission is blocked due to LBT, UE may try to transmit in the nextavailable resource with configured grant.

In an example, Downlink Feedback Information (DFI) may be transmitted(e.g., using DCI) may include HARQ feedback for configured granttransmission. The UE may perform transmission/retransmission usingconfigured grant according to DFI including HARQ feedback. In anexample, wideband carrier with more than one channels is supported onNR-based unlicensed cell.

In an example, there may be one active BWP in a carrier. In an example,a BWP with multiple channels may be activated. In an example, whenabsence of Wi-Fi cannot be guaranteed (e.g. by regulation), LBT may beperformed in units of 20 MHz. In this case, there may be multipleparallel LBT procedures for this BWP. The actual transmission bandwidthmay be subject to subband with LBT success, which may result in dynamicbandwidth transmission within this active wideband BWP.

In an example, multiple active BWPs may be supported. To maximize theBWP utilization efficiency, the BWP bandwidth may be the same as thebandwidth of subband for LBT, e.g., LBT is carried out on each BWP. Thenetwork may activate/deactivate the BWPs based on data volume to betransmitted.

In an example, multiple non overlapped BWPs may be activated for a UEwithin a wide component carrier, which may be similar as carrieraggregation in LTE LAA. To maximize the BWP utilization efficiency, theBWP bandwidth may be the same as the bandwidth of subband for LBT, i.e.LBT is carrier out on each BWP. When more than one subband LBT success,it requires UE to have the capability to support multiple narrow RF or awide RF which includes these multiple activated BWPs.

In an example, a single wideband BWP may be activated for a UE within acomponent carrier. The bandwidth of wideband BWP may be in the unit ofsubband for LBT. For example, if the subband for LBT is 20 MHz in 5 GHzband, the wideband BWP bandwidth may consist of multiple 20 MHz. Theactual transmission bandwidth may be subject to subband with LBTsuccess, which may result in dynamic bandwidth transmission within thisactive wideband BWP.

In an example, active BWP switching may be achieved by use of schedulingDCI. In an example, the network may indicate to the UE a new active BWPto use for an upcoming, and any subsequent, data transmission/reception.In an example, a UE may monitor multiple, configured BWPs to determinewhich has been acquired for DL transmissions by the gNB. For example, aUE may be configured with monitoring occasion periodicity and offset foreach configured BWP. The UE may attempt to determine if a BWP has beenacquired by the gNB during those monitoring occasions. In an example,upon successfully determining that the channel is acquired, the UE maycontinue with that BWP as its active BWP, at least until indicatedotherwise or MCOT has been reached. In an example, when a UE hasdetermined that a BWP is active, it may attempt blind detection of PDCCHin configured CORESETs and it might also perform measurements onaperiodic or SPS resources.

In an example, for UL transmissions, a UE may be configured withmultiple UL resources, possibly in different BWPs. The UE may havemultiple LBT configurations, each tied to a BWP and possibly a beam pairlink. The UE may be granted UL resources tied to one or more LBTconfigurations. Similarly, the UE may be provided with multipleAUL/grant-free resources each requiring the use of different LBTconfigurations. Providing a UE with multiple AUL resources over multipleBWPs may ensure that if LBT fails using a first LBT configuration forone AUL resource in one BWP a UE can attempt transmission in another AULresource in another BWP. This may reduce the channel access latency andmake better use of the over-all unlicensed carrier.

The carrier aggregation with at least one SCell operating in theunlicensed spectrum may be referred to as Licensed-Assisted Access(LAA). In LAA, the configured set of serving cells for a UE may includeat least one SCell operating in the unlicensed spectrum according to afirst frame structure (e.g., frame structure Type 3). The SCell may becalled LAA SCell.

In an example, if the absence of IEEE802.11n/llac devices sharing thecarrier cannot be guaranteed on a long term basis (e.g., by level ofregulation), and for if the maximum number of unlicensed channels thatnetwork may simultaneously transmit on is equal to or less than 4, themaximum frequency separation between any two carrier center frequencieson which LAA SCell transmissions are performed may be less than or equalto 62 MHz. In an example, the UE may be required to support frequencyseparation.

In an example, base station and UE may apply Listen-Before-Talk (LBT)before performing a transmission on LAA SCell. When LBT is applied, thetransmitter may listen to/sense the channel to determine whether thechannel is free or busy. If the channel is determined to be free/clear,the transmitter may perform the transmission; otherwise, it may notperform the transmission. In an example, if base station uses channelaccess signals of other technologies for the purpose of channel access,it may continue to meet the LAA maximum energy detection thresholdrequirement.

In an example, the combined time of transmissions compliant with thechannel access procedure by a base station may not exceed 50 ms in anycontiguous 1 second period on an LAA SCell.

In an example, which LBT type (e.g., type 1 or type 2 uplink channelaccess) the UE applies may be signalled via uplink grant for uplinkPUSCH transmission on LAA SCells. In an example, for Autonomous Uplink(AUL) transmissions the LBT may not be signalled in the uplink grant.

In an example, for type 1 uplink channel access on AUL, base station maysignal the Channel Access Priority Class for a logical channel and UEmay select the highest Channel Access Priority Class (e.g., with a lowernumber in FIG. 16) of the logical channel(s) with MAC SDU multiplexedinto the MAC PDU. In an example, the MAC CEs except padding BSR may usethe lowest Channel Access Priority Class.

In an example, for type 2 uplink channel access on AUL, the UE mayselect logical channels corresponding to any Channel Access PriorityClass for UL transmission in the subframes signalled by base station incommon downlink control signaling.

In an example, for uplink LAA operation, the base station may notschedule the UE more subframes than the minimum necessary to transmitthe traffic corresponding to the selected Channel Access Priority Classor lower (e.g., with a lower number in FIG. 16), than the channel AccessPriority Class signalled in UL grant based on the latest BSR andreceived uplink traffic from the UE if type 1 uplink channel accessprocedure is signalled to the UE; and/or Channel Access Priority Classused by the base station based on the downlink traffic, the latest BSRand received UL traffic from the UE if type 2 uplink channel accessprocedure is signalled to the UE.

In an example, a first number (e.g., four) Channel Access PriorityClasses may be used when performing uplink and downlink transmissions inLAA carriers. In an example in FIG. 16 shows which Channel AccessPriority Class may be used by traffic belonging to the differentstandardized QCIs. A non-standardized QCI (e.g., Operator specific QCI)may use suitable Channel Access Priority Class based on the FIG. 16 forexample, e.g., the Channel Access Priority Class used for anon-standardized QCI should be the Channel Access Priority Class of thestandardized QCIs which best matches the traffic class of thenon-standardized QCI.

In an example, for uplink, the base station may select the ChannelAccess Priority Class by taking into account the lowest priority QCI ina Logical Channel Group.

In an example, four Channel Access Priority Classes may be used. If a DLtransmission burst with PDSCH is transmitted, for which channel accesshas been obtained using Channel Access Priority Class P (1 . . . 4), thebase station may ensure the following where a DL transmission burstrefers to the continuous transmission by base station after a successfulLBT: the transmission duration of the DL transmission burst may notexceed the minimum duration needed to transmit all available bufferedtraffic corresponding to Channel Access Priority Class(es)≤P; thetransmission duration of the DL transmission burst may not exceed theMaximum Channel Occupancy Time for Channel Access Priority Class P; andadditional traffic corresponding to Channel Access Priority Class(s)>Pmay be included in the DL transmission burst once no more datacorresponding to Channel Access Priority Class≤P is available fortransmission. In such cases, base station may maximise occupancy of theremaining transmission resources in the DL transmission burst with thisadditional traffic.

In an example, when the PDCCH of an LAA SCell is configured, ifcross-carrier scheduling applies to uplink transmission, it may bescheduled for downlink transmission via its PDCCH and for uplinktransmission via the PDCCH of one other serving cell. In an example,when the PDCCH of an LAA SCell is configured, if self-scheduling appliesto both uplink transmission and downlink transmission, it may bescheduled for uplink transmission and downlink transmission via itsPDCCH.

In an example, Autonomous uplink may be supported on the SCells. In anexample, one or more autonomous uplink configuration may be supportedper SCell. In an exampe, multiple autonomous uplink configurations maybe active simultaneously when there is more than one SCell.

In an example, when autonomous uplink is configured by RRC, thefollowing information may be provided in an AUL configurationinformation element (e.g., AUL-Config): AUL C-RNTI; HARQ process IDsaul-harq-processes that may be configured for autonomous UL HARQoperation, the time period aul-retransmissionTimer before triggering anew transmission or a retransmission of the same HARQ process usingautonomous uplink; the bitmap aul-subframes that indicates the subframesthat are configured for autonomous UL HARQ operation.

In an example, when the autonomous uplink configuration is released byRRC, the corresponding configured grant may be cleared.

In an example, if AUL-Config is configured, the MAC entity may considerthat a configured uplink grant occurs in those subframes for whichaul-subframes is set to 1.

In an example, if AUL confirmation has been triggered and not cancelled,if the MAC entity has UL resources allocated for new transmission forthis TTI, the MAC entity may instruct a Multiplexing and Assemblyprocedure to generate an AUL confirmation MAC Control Element; the MACentity may cancel the triggered AUL confirmation.

In an example, the MAC entity may clear the configured uplink grant forthe SCell in response first transmission of AUL confirmation MAC ControlElement triggered by the AUL release for this SCell. In an example,retransmissions for uplink transmissions using autonomous uplink maycontinue after clearing the corresponding configured uplink grant.

In an example, a MAC entity may be configured with AUL-RNTI for AULoperation.

In an example, an uplink grant may be received for a transmssion timeinterval for a Serving Cell on the PDCCH for the MAC entity's AULC-RNTI. In an example, if the NDI in the received HARQ information is 1,the MAC entity may consider the NDI for the corresponding HARQ processnot to have been toggled. The MAC entity may deliver the uplink grantand the associated HARQ information to the HARQ entity for thistransmisison time interval. In an example, if the NDI in the receivedHARQ information is 0 and if PDCCH contents indicate AUL release, theMAC entity may trigger an AUL confirmation. If an uplink grant for thisTTI has been configured, the MAC entity may consider the NDI bit for thecorresponding HARQ process to have been toggled. The MAC entity maydeliver the configured uplink grant and the associated HARQ informationto the HARQ entity for this TTI. In an example, if the NDI in thereceived HARQ information is 0 and if PDCCH contents indicate AULactivation, the MAC entity may trigger an AUL confirmation.

In an example, if the aul-retransmissionTimer is not running and ifthere is no uplink grant previously delivered to the HARQ entity for thesame HARQ process; or if the previous uplink grant delivered to the HARQentity for the same HARQ process was not an uplink grant received forthe MAC entity's C-RNTI; or if the HARQ_FEEDBACK is set to ACK for thecorresponding HARQ process, the MAC entity may deliver the configureduplink grant, and the associated HARQ information to the HARQ entity forthis TTI.

In an example, the NDI transmitted in the PDCCH for the MAC entity's AULC-RNTI may be set to 0.

In an example, for configured uplink grants, if UL HARQ operation isautonomous, the HARQ Process ID associated with a TTI for transmissionon a Serving Cell may be selected by the UE implementation from the HARQprocess IDs that are configured for autonomous UL HARQ operation byupper layers for example, in aul-harq-processes.

In an example, for autonomous HARQ, a HARQ process may maintain a statevariable e.g., HARQ_FEEDBACK, which may indicate the HARQ feedback forthe MAC PDU currently in the buffer, and/or a timeraul-retransmissionTimer which may prohibit new transmission orretransmission for the same HARQ process when the timer is running

In an example, when the HARQ feedback is received for a TB, the HARQprocess may set HARQ_FEEDBACK to the received value; and may stop theaul-retransmissionTimer if running

In an example, when PUSCH transmission is performed for a TB and if theuplink grant is a configured grant for the MAC entity's AUL C-RNTI, theHARQ process start the aul-retransmissionTimer.

In an example, if the HARQ entity requests a new transmission, the HARQprocess may set HARQ_FEEDBACK to NACK if UL HARQ operation is autonomousasychronous. if the uplink grant was addressed to the AUL C-RNTI, setCURRENT_IRV to 0.

In an example, if aperiodic CSI requested for a TTI, the MAC entity maynot generate a MAC PDU for the HARQ entity in case the grant indicatedto the HARQ entity is a configured uplink grant activated by the MACentity's AUL C-RNTI.

In an example, if the UE detects on the scheduling cell for ULtransmissions on an LAA SCell a transmission of DCI (e.g., Format 0A/4A)with the CRC scrambled by AUL C-RNTI carrying AUL-DFI, the UE may usethe autonomous uplink feedback information according to the followingprocedures: for a HARQ process configured for autonomous uplinktransmission, the corresponding HARQ-ACK feedback may be delivered tohigher layers. For the HARQ processes not configured for autonomousuplink transmission, the corresponding HARQ-ACK feedback may notdelivered to higher layers; for an uplink transmission insubframe/slot/TTI n, the UE may expect HARQ-ACK feedback in the AUL-DFIat earliest in subframe n+4; If the UE receives AUL-DFI in a subframeindicating ACK for a HARQ process, the UE may not be expected to receiveAUL-DFI indicating ACK for the same HARQ process prior to 4 ms after theUE transmits another uplink transmission associated with that HARQprocess;

In an example, a UE may validate an autonomous uplink assignmentPDCCH/EPDCCH if all the following conditions are met: the CRC paritybits obtained for the PDCCH/EPDCCH payload are scrambled with the AULC-RNTI; and the ‘Flag for AUL differentiation’ indicatesactivating/releasing AUL transmission. In an example, one or more fieldsin an activation DCI may be pre-configured values for validation.

In an example, a BWP IE may be used to configure a bandwidth part. For aserving cell the network may configure at least an initial bandwidthpart comprising of at least a downlink bandwidth part and one (if theserving cell is configured with an uplink) or two (if usingsupplementary uplink (SUL)) uplink bandwidth parts. In an example, thenetwork may configure additional uplink and downlink bandwidth parts fora serving cell.

In an example, the bandwidth part configuration may be split into uplinkand downlink parameters and into common and dedicated parameters. Commonparameters (e.g., in BWP-UplinkCommon and BWP-DownlinkCommon) may becell specific and the network may ensure the necessary alignment withcorresponding parameters of other UEs. In an example, the commonparameters of the initial bandwidth part of the PCell may be providedvia system information. In an example, for other serving cells, thenetwork may provide the common parameters via dedicated signalling. Anexample BWP information element is shown below:

BWP ::= SEQUENCE {  locationAndBandwidth INTEGER (0..37949), subcarrierSpacing SubcarrierSpacing,  cyclicPrefix ENUMERATED {extended } OPTIONAL  -- Need R } BWP-Uplink ::= SEQUENCE {  bwp-IdBWP-Id,  bwp-Common BWP-UplinkCommon OPTIONAL, -- Need M  bwp-DedicatedBWP-UplinkDedicated OPTIONAL, -- Need M } BWP-UplinkCommon ::= SEQUENCE{  genericParameters BWP,  rach-ConfigCommon SetupRelease {RACH-ConfigCommon } OPTIONAL, -- Need M  pusch-ConfigCommon SetupRelease{ PUSCH-ConfigCommon } OPTIONAL, -- Need M  pucch-ConfigCommonSetupRelease { PUCCH-ConfigCommon } OPTIONAL, -- Need M  ... }BWP-UplinkDedicated ::=  SEQUENCE {  pucch-Config SetupRelease {PUCCH-Config } OPTIONAL, -- Need M  pusch-Config SetupRelease {PUSCH-Config } OPTIONAL, -- Cond SetupOnly  configuredGrantConfigSetupRelease { ConfiguredGrantConfig } OPTIONAL, -- Need M  srs-ConfigSetupRelease { SRS-Config } OPTIONAL, -- Need M beamFailureRecoveryConfig SetupRelease { BeamFailureRecoveryConfig }OPTIONAL, -- Cond SpCellOnly  ... } BWP-Downlink ::=  SEQUENCE {  bwp-Id BWP-Id,  bwp-Common BWP-DownlinkCommon OPTIONAL, -- Need M bwp-Dedicated  BWP-DownlinkDedicated OPTIONAL, -- Need M  ... }BWP-DownlinkCommon ::= SEQUENCE {  genericParameters  BWP, pdcch-ConfigCommon SetupRelease { PDCCH-ConfigCommon } OPTIONAL, --Need M  pdsch-ConfigCommon SetupRelease { PDSCH-ConfigCommon }OPTIONAL, -- Need M  ... } BWP-DownlinkDedicated ::= SEQUENCE { pdcch-Config  SetupRelease { PDCCH-Config } OPTIONAL, -- Need M pdsch-Config SetupRelease { PDSCH-Config } OPTIONAL, -- Need M sps-Config SetupRelease { SPS-Config } OPTIONAL, -- Need M radioLinkMonitoringConfig SetupRelease { RadioLinkMonitoringConfig }OPTIONAL, -- Need M  ... }

In an example, cyclicPrefix may indicate whether to use the extendedcyclic prefix for this bandwidth part. If not set, the UE may use thenormal cyclic prefix. In an example, normal CP may be supported for allnumerologies and slot formats. Extended CP may be supported only for 60kHz subcarrier spacing. In an example, locationAndBandwidth may indicatefrequency domain location and bandwidth of a bandwidth part. The valueof the field may be interpreted as resource indicator value (RIV). In anexample, the first PRB may be a PRB determined by subcarrierSpacing ofthis BWP and offsetToCarrier (for example, configured inSCS-SpecificCarrier contained within FrequencyInfoDL) corresponding tothis subcarrier spacing. In case of TDD, a BWP-pair (UL BWP and DL BWPwith the same bwp-Id) may have the same center frequency.

In an example, subcarrierSpacing may indicate subcarrier spacing to beused in this BWP for all channels and reference signals unlessexplicitly configured elsewhere. The value kHz 15 may correspond to μ=0,kHz 30 to μ=1, and so on. In an example, bwp-Id may indicate anidentifier for a bandwidth part. In an example, the BWP ID=0 beassociated with the initial BWP. In an example, the NW may trigger theUE to switch UL or DL BWP using a DCI field. The four code points inthat DCI field map to the RRC-configured BWP-ID may be for up to 3configured BWPs (in addition to the initial BWP) the DCI code point maybe equivalent to the BWP ID (initial=0, first dedicated=1, . . . ). Inan example, if the NW configures 4 dedicated bandwidth parts, they areidentified by DCI code points 0 to 3. In an example,radioLinkMonitoringConfig may indicate UE specific configuration ofradio link monitoring for detecting cell- and beam radio link failureoccasions. In an example, bwp-Id may indicate an identifier for abandwidth part. In an example, the BWP ID=0 may be associated with theinitial BWP. In an example, the NW may trigger the UE to switch UL or DLBWP using a DCI field. The four code points in that DCI field map to theRRC-configured BWP-ID may be: For up to 3 configured BWPs (in additionto the initial BWP) the DCI code point is equivalent to the BWP ID(initial=0, first dedicated=1, . . . ). If the NW configures 4 dedicatedbandwidth parts, they are identified by DCI code points 0 to 3.

In an example, an information element (e.g., FrequencyInfoUL) mayprovide basic parameters of an uplink carrier and transmission thereon.In an example, a field FDD-OrSUL may be present if this informationelement (e.g., FrequencyInfoUL) is for the paired UL for a DL (e.g.,defined in a FrequencyInfoDL) or if this FrequencyInfoUL is for asupplementary uplink (SUL). It is absent otherwise (e.g., if thisFrequencyInfoUL is for an unpaired UL (TDD)). In an example, a field(e.g., FDD-OrSUL) may be present if this FrequencyInfoUL is for thepaired UL for a DL (e.g., defined in a FrequencyInfoDL) or if thisFrequencyInfoUL is for a supplementary uplink (SUL). It may be absentotherwise.

In an example, an information element (e.g., PUSCH-TPC-CommandConfig)may be used to configure the UE for extracting TPC commands for PUSCHfrom a group-TPC messages on DCI. In an example, a field SUL-Only may bepresent if this serving cell is configured with a supplementary uplink(SUL). It may be absent otherwise.

In an example, an information element ServingCellConfig may be used toconfigure (add or modify) the UE with a serving cell, which may be theSpCell or an SCell of an MCG or SCG. The parameters may be UE specificand/or cell specific (e.g. in additionally configured bandwidth parts).In an example, a ServCellAdd-SUL may be present upon serving celladdition (e.g., for PSCell and SCell) provided that the serving cell isconfigured with a supplementary uplink.

In an example, an information element ServingCellConfigCommon may beused to configure cell specific parameters of a UE's serving cell. TheIE may contain parameters which a UE would typically acquire from SSB,MIB or SIBs when accessing the cell from IDLE. With this IE, the networkmay provide this information in dedicated signaling when configuring aUE with a SCells or with an additional cell group (SCG). It may provideit for SpCells (MCG and SCG) upon reconfiguration with sync. In anexample, a ServCellAdd-SUL may be present upon serving cell addition(e.g., for PSCell and SCell) provided that the serving cell isconfigured with a supplementary uplink.

In an example, a BWP-UplinkDedicated field ConfiguredGrantConfig mayindicate a configured-grant of type 1 or type 2. In an example, it maybe configured for UL or SUL but in case of type 1 not for both at atime. In an example, a pucch-Config field may indicate PUCCHconfiguration for one BWP of the regular UL or SUL of a serving cell. Ifthe UE is configured with SUL, the network may configure PUCCH on theBWPs of one of the uplinks (UL or SUL). The network may configurePUCCH-Config for each SpCell. If supported by the UE, the network mayconfigure at most one additional SCell of a cell group with PUCCH-Config(e.g., PUCCH SCell). In an example, a pusch-Config may indicate PUSCHconfiguration for one BWP of a regular UL or SUL of a serving cell. Inan example, if the UE is configured with SUL and if it has aPUSCH-Config for both UL and SUL, a carrier indicator field in DCI mayindicate for which of the two to use an UL grant.

In an example, a RACH-ConfigCommon IE may comprise arsrp-ThresholdSSB-SUL field indicating a threshold where the UE selectsSUL carrier to perform random access based on the threshold.

In an example, the Supplementary UL (SUL) carrier may be configured as acomplement to the normal UL (NUL) carrier. In an example, switchingbetween the NUL carrier and the SUL carrier means that the ULtransmissions move from the PUSCH on one carrier to the other carrier.In an example, this may be done via an indication in DCI. In an example,if the MAC entity receives a UL grant indicating a SUL switch while aRandom Access procedure is ongoing, the MAC entity may ignore the ULgrant. In an example, the Serving Cell configured withsupplementaryUplink may belong to a single TAG.

In an example, if a UE is configured with two UL carriers for a servingcell and the UE determines a Type 1 power headroom report for theserving cell based on a reference PUSCH transmission, the UE may computea Type 1 power headroom report for the serving cell assuming a referencePUSCH transmission on the UL carrier provided by higher layer parameterpusch-Config. If the UE is provided higher layer parameter pusch-Configfor both UL carriers, the UE may compute a Type 1 power headroom reportfor the serving cell assuming a reference PUSCH transmission on the ULcarrier provided by higher layer parameter pucch-Config. If pucch-Configis not configured, the UE may compute a Type 1 power headroom report forthe serving cell assuming a reference PUSCH transmission on thenon-supplementary UL carrier.

In an example, an initial active DL BWP may be defined by a location andnumber of contiguous PRBs, a subcarrier spacing, and a cyclic prefix,for the control resource set for Type0-PDCCH common search space. Foroperation on the primary cell or on a secondary cell, a UE may beprovided an initial active UL BWP by higher layer parameterinitialuplinkBWP. If the UE is configured with a supplementary carrier,the UE may be provided an initial UL BWP on the supplementary carrier byhigher layer parameter initialUplinkBWP in supplementaryUplink.

In an example, if a UE is configured by higher layer parameterfirstActiveDownlinkBWP-Id a first active DL BWP and by higher layerparameter firstActiveUplinkBWP-Id a first active UL BWP on a secondarycell or supplementary carrier, the UE may use the indicated DL BWP andthe indicated UL BWP on the secondary cell as the respective firstactive DL BWP and first active UL BWP on the secondary cell orsupplementary carrier.

In an example, an information element (e.g., LBT-Config) may indicateone or more parameters for listen before talk operation at the wirelessdevice. In an example, maxEnergyDetectionThreshold may indicate anabsolute maximum energy detection threshold value. In an example, theunits of maxEnergyDetectionThreshold may be in dBm. For example, value−85 may correspond to −85 dBm, value −84 may correspond to −84 dBm, andso on (e.g., in steps of ldBm). If the field is not configured, the UEshall use a default maximum energy detection threshold value. In anexample, energyDetectionThresholdOffset may indicate an offset to thedefault maximum energy detection threshold value. The unit ofenergyDetectionThresholdOffset may be in dB. For example, value −13 maycorrespond to −13 dB, value −12 may correspond to −12 dB, and so on(e.g., in steps of 1 dB). In an example, an information element (e.g.,laa-SCellSubframeConfig) may indicate a bit-map indicating unlicensedSCell subframe configuration. For example, 1 denotes that thecorresponding subframe is allocated as MBSFN subframe. The bitmap may beinterpreted as follows: Starting from the first/leftmost bit in thebitmap, the allocation applies to subframes #1, #2, #3, #4, #6, #7, #8,and #9. In an example, a cell/bandwidth part may be configured with aninformation element (e.g., CrossCarrierSchedulingConfigLAA) that mayindicate a scheduling cell ID and a CIF value. In an example, aninformation element schedulingCellId may indicate which cell signals thedownlink allocations and uplink grants, if applicable, for the concernedSCell. In case the UE is configured with DC, the scheduling cell may bepart of the same cell group (e.g., MCG or SCG) as the scheduled cell. Incase the UE is configured with crossCarrierSchedulingConfigLAA-UL,schedulingCellId indicated in crossCarrierSchedulingConfigLAA-UL mayindicate which cell signals the uplink grants. In an example, aninformation element (e.g., cifInSchedulingCell) may indicate the CIFvalue used in the scheduling cell to indicate the cell.

In an example, a UE and a base station scheduling UL transmission(s) forthe UE may perform channel access procedures for the UE to access thechannel(s) on which the unlicensed Scell(s) transmission(s) areperformed.

In an example, the UE may access a carrier on which unlicensed Scell(s)UL transmission(s) are performed according to one of a plurality ofchannel access procedures. In an example, the plurality of channelaccess procedures may comprise a first Type or a second Type UL channelaccess procedures.

In an example, if an UL grant scheduling a PUSCH transmission indicatesa first Type channel access procedure, the UE may use the first Typechannel access procedure for transmitting transmissions including thePUSCH transmission.

In an example, a UE may use a first Type channel access procedure fortransmitting transmissions including the PUSCH transmission onautonomous UL resources.

In an example, if an UL grant scheduling a PUSCH transmission indicatesa second Type channel access procedure, the UE may use the second Typechannel access procedure for transmitting transmissions including thePUSCH transmission.

In an example and as shown in FIG. 18, channel access procedure fortransmission of a first PUSCH may be based on a first Type channelaccess. The first Type channel access may be based on sensing thechannel for a first number of durations (e.g., CCA slots). The firstduration may have a first fixed value. The first number may be based ona random number drawn from an interval based on the priority class. Inan example, channel access procedure for transmission of a second PUSCHmay be based on a second Type channel access. The second Type channelaccess procedure may be based on sensing the channel based on a secondfixed duration.

In an example, the UE may use the first Type channel access procedurefor transmitting SRS transmissions not including a PUSCH transmission.In an example, UL channel access priority class p=1 may be used for SRStransmissions not including a PUSCH.

In an example, if the UE is scheduled to transmit PUSCH and SRS insubframe/slot/mini-slot/TTI n, and if the UE cannot access the channelfor PUSCH transmission in subframe/slot/mini-slot/TTI n, the UE mayattempt to make SRS transmission in subframe/slot/mini-slot/TTI naccording to uplink channel access procedures specified for SRStransmission.

T_(ulm cot,p) configure an UL offset l and an UL duration d forsubframe/slot/mini-slot/TTI n and one or more second fields (e.g., COTsharing indication for AUL field) are set to true, a UE configured withautonomous UL may use the second Type channel access for autonomous ULtransmissions corresponding to any priority class insubframes/slots/mini-slots/TTIs n+l+i where i=0, 1, . . . , d−1, if theend of UE autonomous UL transmission occurs in or beforesubframe/slot/mini-slot/TTI n+l+d−1 and the autonomous UL transmissionbetween n+l and n+l+d−1 may be contiguous.

In an example, if one or more first fields (e.g., an UL duration andoffset field) configures an UL offset l and an UL duration d forsubframe/slot/mini-slot/TTI n and one or more second fields (e.g., a COTsharing indication for AUL field) is set to false, a UE configured withautonomous UL may not transmit autonomous UL insubframes/slots/mini-slots/TTIs n+l+i where i=0, 1, . . . d−1.

In an example, if the UE scheduled to transmit transmissions includingPUSCH in a set subframes/slots/mini-slots/TTIs n₀, n₁, . . . , n_(w-1)using one or more PDCCH DCI Formats and if the UE cannot access thechannel for a transmission in subframe/slot/mini-slot/TTI n_(k), the UEmay attempt to make a transmission in subframe/slot/mini-slot/TTIn_(k+1) according to a channel access type indicated in the DCI, wherek∈{0,1, . . . w−2}, and w is the number of scheduledsubframes/slots/mini-slots/TTIs indicated in the DCI.

In an example, if the UE is scheduled to transmit transmissions withoutgaps including PUSCH in a set of subframes/slots/mini-slots/TTIs n₀, n₁,. . . , n_(w-1) using one or more PDCCH DCI Formats and the UE performsa transmission in subframe/slot/mini-slot/TTI n_(k) after accessing thecarrier according to one of first Type or second Type UL channel accessprocedures, the UE may continue transmission insubframes/slots/mini-slots/TTIs after n_(k) where k∈{0,1, . . . w−1}.

In an example, if the beginning of UE transmission insubframe/slot/mini-slot/TTI n+1 immediately follows the end of UEtransmission in subframe/slot/mini-slot/TTI n, the UE may not beexpected to be indicated with different channel access types for thetransmissions in those subframes/slots/mini-slots/TTIs.

In an example, if a UE is scheduled to transmit transmissions includinga first mode PUSCH in a set subframes/slots/mini-slots/TTIs n₀, n₁, . .. , n_(w-1) using one or more PDCCH DCI Formats and a first Type channelaccess procedure, and if the UE cannot access the channel for atransmission in subframe/slot/mini-slot/TTI n_(k) according to the PUSCHstarting position indicated in the DCI, the UE may attempt to make atransmission in subframe/slot/mini-slot/TTI n_(k) with an offset ofo_(i) OFDM symbol and according to the channel access type indicated inthe DCI, where k∈{0,1, . . . w−1} and i∈{0,7}, for i=0 the attempt ismade at the PUSCH starting position indicated in the DCI, and w is thenumber of scheduled subframes/slots/mini-slots/TTIs indicated in theDCI. In an example, there may be no limit on the number of attempts theUE should make for the transmission.

In an example, if the UE is scheduled to transmit transmissionsincluding a first mode PUSCH in a set subframes/slots/mini-slots/TTIsn₀, n₁, . . . , n_(w-1) using one or more PDCCH DCIs and a second Typechannel access procedure, and if the UE cannot access the channel for atransmission in subframe/slot/mini-slot/TTI n_(k) according to the PUSCHstarting position indicated in the DCI, the UE may attempt to make atransmission in subframe/slot/mini-slot/TTI n_(k) with an offset ofo_(i) OFDM symbol and according to the channel access type indicated inthe DCI, where k∈{0,1, . . . w−1} and i∈{0,7}, for i=0 the attempt ismade at the PUSCH starting position indicated in the DCI, and w is thenumber of scheduled subframes/slots/mini-slots/TTIs indicated in theDCI. In an example, the number of attempts the UE may make for thetransmission may be limited to w+1, where w is the number of scheduledsubframes/slots/mini-slots/TTIs indicated in the DCI.

In an example, if a UE is scheduled to transmit without gaps insubframes/slots/mini-slots/TTIs n₀, n₁, . . . , n_(w-1) using one ormore PDCCH DCI Formats, and if the UE has stopped transmitting during orbefore subframe/slot/mini-slot/TTI n_(k1), k1∈{0,1, . . . w−2}, and ifthe channel is sensed by the UE to be continuously idle after the UE hasstopped transmitting, the UE may transmit in a latersubframe/slot/mini-slot/TTI n_(k2), k2∈{1, . . . w−1} using a secondType channel access procedure. If the channel sensed by the UE is notcontinuously idle after the UE has stopped transmitting, the UE maytransmit in a later subframe/slot/mini-slot/TTI n_(k2), k2∈{1, . . .w−1} using a first Type channel access procedure with the UL channelaccess priority class indicated in the DCI corresponding tosubframe/slot/mini-slot/TTI n_(k2).

In an example, if the UE receives an UL grant and the DCI indicates aPUSCH transmission starting in subframe/slot/mini-slot/TTI n using sfirst Type channel access procedure, and if the UE has an ongoing firstType channel access procedure before subframe/slot/mini-slot/TTI n: if aUL channel access priority class value p₁ used for the ongoing firstType channel access procedure is same or larger than the UL channelaccess priority class value p₂ indicated in the DCI, the UE may transmitthe PUSCH transmission in response to the UL grant by accessing thecarrier by using the ongoing first Type channel access procedure.

In an example, if the UE receives an UL grant and the DCI indicates aPUSCH transmission starting in subframe/slot/mini-slot/TTI n using sfirst Type channel access procedure, and if the UE has an ongoing firstType channel access procedure before subframe/slot/mini-slot/TTI n: ifthe UL channel access priority class value p₁ used for the ongoing firstType channel access procedure is smaller than the UL channel accesspriority class value p₂ indicated in the DCI, the UE may terminate theongoing channel access procedure.

In an example, if the UE is scheduled to transmit on a set of carriers Cin subframe/slot/mini-slot/TTI n, and if the UL grants scheduling PUSCHtransmissions on the set of carriers C indicate a first Type channelaccess procedure, and if the same PUSCH starting position is indicatedfor all carriers in the set of carriers C, or if the UE intends toperform an autonomous uplink transmission on the set of carriers C insubframe/slot/mini-slot/TTI n with first Type channel access procedure,and if the same N_(Start) ^(FS3) is used for all carriers in the set ofcarriers C: the UE may transmit on carrier c_(i)∈C using a second Typechannel access procedure, if the second Type channel access procedure isperformed on carrier c_(i) immediately before the UE transmission oncarrier c_(j)∈C, i≠j, and if the UE has accessed carrier c_(j) usingfirst Type channel access procedure, where carrier c_(j) is selected bythe UE uniformly randomly from the set of carriers C before performingthe first Type channel access procedure on any carrier in the set ofcarriers C.

In an example, if the UE is scheduled to transmit on carrier c_(i) by aUL grant received on carrier c_(j), i≠j, and if the UE is transmittingusing autonomous UL on carrier c_(i), the UE may terminate the ongoingPUSCH transmissions using the autonomous UL at least onesubframe/slot/mini-slot/TTI before the UL transmission according to thereceived UL grant.

In an example, if the UE is scheduled by a UL grant received on acarrier to transmit a PUSCH transmission(s) starting fromsubframe/slot/mini-slot/TTI n on the same carrier using first Typechannel access procedure and if at least for the first scheduledsubframe/slot/mini-slot/TTI occupies N_(RB) ^(UL) resource blocks andthe indicated ‘PUSCH starting position is OFDM symbol zero, and if theUE starts autonomous UL transmissions before subframe/slot/mini-slot/TTIn using first Type channel access procedure on the same carrier, the UEmay transmit UL transmission(s) according to the received UL grant fromsubframe/slot/mini-slot/TTI n without a gap, if the priority class valueof the performed channel access procedure is larger than or equal topriority class value indicated in the UL grant, and the autonomous ULtransmission in the subframe/slot/mini-slot/TTI precedingsubframe/slot/mini-slot/TTI n may end at the last OFDM symbol of thesubframe/slot/mini-slot/TTI regardless of the higher layer parameterAulEndingPosition. The sum of the lengths of the autonomous ULtransmission(s) and the scheduled UL transmission(s) may not exceed themaximum channel occupancy time corresponding to the priority class valueused to perform the autonomous uplink channel access procedure.Otherwise, the UE may terminate the ongoing autonomous UL transmissionat least one subframe/slot/mini-slot/TTI before the start of the ULtransmission according to the received UL grant on the same carrier.

In an example, a base station may indicate a second Type channel accessprocedure in the DCI of an UL grant scheduling transmission(s) includingPUSCH on a carrier in subframe/slot/mini-slot/TTI n when the basestation has transmitted on the carrier according to a channel accessprocedure, or when a base station may indicate using the ‘UL durationand offset’ field that the UE may perform a second Type channel accessprocedure for transmissions(s) including PUSCH on a carrier insubframe/slot/mini-slot/TTI n when the base station has transmitted onthe carrier according to a channel access procedure, or when a basestation may indicate using the ‘UL duration and offset’ field and ‘COTsharing indication for AUL’ field that a UE configured with autonomousUL may perform a second Type channel access procedure for autonomous ULtransmissions(s) including PUSCH on a carrier insubframe/slot/mini-slot/TTI n when the base station has transmitted onthe carrier according to a channel access procedure and acquired thechannel using the largest priority class value and the base stationtransmission includes PDSCH, or when or when a base station may scheduletransmissions including PUSCH on a carrier insubframe/slot/mini-slot/TTI n, that follows a transmission by the basestation on that carrier with a duration of T_(short_ul)=25 us, ifsubframe/slot/mini-slot/TTI n occurs within the time interval startingat t₀ and ending at t₀+T_(CO), where T_(CO)=T_(m,cot,p)+T_(g), where t₀may be the time instant when the base station has started transmission,T_(m,cot,p) value may be determined by the base station, T_(g) may betotal duration of all gaps of duration greater than 25 us that occurbetween the DL transmission of the base station and UL transmissionsscheduled by the base station, and between any two UL transmissionsscheduled by the base station starting from t₀.

In an example, the base station may schedule UL transmissions between t₀and t₀+T_(CO) in contiguous subframes/slots/mini-slots/TTIs if they canbe scheduled contiguously.

In an example, for an UL transmission on a carrier that follows atransmission by the base station on that carrier within a duration ofT_(short_ul)=25 us, the UE may use a second Type channel accessprocedure for the UL transmission.

In an example, if the base station indicates second Type channel accessprocedure for the UE in the DCI, the base station may indicate thechannel access priority class used to obtain access to the channel inthe DCI.

In an example, the UE may transmit the transmission using first Typechannel access procedure after first sensing the channel to be idleduring the slot durations of a defer duration T_(d); and after thecounter N is zero in step 4. In an example, the counter N may beadjusted by sensing the channel for additional slot duration(s)according to a procedure.

In an example, if the UE has not transmitted a transmission includingPUSCH or SRS on a carrier on which unlicensed Scell(s) transmission(s)are performed, the UE may transmit a transmission including PUSCH or SRSon the carrier, if the channel is sensed to be idle at least in a slotduration T_(sl) when the UE is ready to transmit the transmissionincluding PUSCH or SRS, and if the channel has been sensed to be idleduring all the slot durations of a defer duration T_(d) immediatelybefore the transmission including PUSCH or SRS. If the channel has notbeen sensed to be idle in a slot duration T_(si) when the UE firstsenses the channel after it is ready to transmit, or if the channel hasnot been sensed to be idle during any of the slot durations of a deferduration T_(d) immediately before the intended transmission includingPUSCH or SRS, the UE may proceeds to step 1 after sensing the channel tobe idle during the slot durations of a defer duration T_(d).

In an example, the defer duration T_(d) may consist of duration T_(f)=16us immediately followed by m_(p) consecutive slot durations where eachslot duration is T_(si)=9 us, and T_(f) may include an idle slotduration T_(sl) at start of T_(f).

In an example, a slot duration T_(sl) may be considered to be idle ifthe UE senses the channel during the slot duration, and the powerdetected by the UE for at least 4 us within the slot duration is lessthan energy detection threshold X_(Thresh). Otherwise, the slot durationT_(sl) may be considered to be busy.

In an example, CW_(min,p)≤CW_(p)≤CW_(max,p) may be the contentionwindow. In an example, CW_(min,p) and CW_(max,p) may be chosen beforethe channel access procedure. In an example, m_(p), CW_(min,p), andCW_(max,p) may be based on channel access priority class signaled to theUE, as shown in FIG. 17.

In an example, if the UL UE uses second Type channel access procedurefor a transmission including PUSCH, the UE may transmit the transmissionincluding PUSCH immediately after sensing the channel to be idle for atleast a sensing interval T_(short_ul)=25 us. In an example, T_(short_ul)may consists of a duration T_(f)=16 us immediately followed by one slotduration T_(sl)=9 us and T_(f) may include an idle slot duration T_(sl)at start of T_(f). The channel may be considered to be idle forT_(short_ul) if it is sensed to be idle during the slot durations ofT_(short_ul).

In an example, if the UE transmits transmissions using a first Typechannel access procedure that are associated with channel accesspriority class p on a carrier, the UE may maintain the contention windowvalue CW_(p) and may adjust CW_(p) for those transmissions before thechannel access procedure.

In an example, if the UE receives an UL grant or an AUL-DFI, thecontention window size for the priority classes may be adjusted asfollowing: if the NDI value for at least one HARQ process associatedwith HARQ_ID_ref is toggled, or if the HARQ-ACK value(s) for at leastone of the HARQ processes associated with HARQ_ID_ref received in theearliest AUL-DFI after n_(ref)+3 indicates ACK: for every priority classp∈{1,2,3,4} set CW_(p)=CW_(min,p). Otherwise, CW_(p) may be increasedfor every priority class p∈{1,2,3,4} to the next higher allowed value.

In an example, if there exist one or more previous transmissions {T₀, .. . , T_(n)} using the first Type channel access procedure, from thestart subframe(s)/slot(s)/mini-slot(s)/TTI(s) of the previoustransmission(s) of which, N or more subframes/slots/mini-slots/TTIs haveelapsed and neither UL grant nor AUL-DFI was received, where N=max(Contention Window Size adjustment timer X, T_(i) burst length+1) ifX >0 and N=0 otherwise, for each transmission T_(i), CW_(p) is adjustedas following: increase CW_(p) for every priority class p∈{1,2,3,4} tothe next higher allowed value; The CW_(p) is adjusted once. Otherwise ifthe UE transmits transmissions using first Type channel access procedurebefore N subframes/slots/mini-slots/TTIs have elapsed from the start ofprevious UL transmission burst using first Type channel access procedureand neither UL grant nor AUL-DFI is received, the CW_(p) is unchanged.

In an example, if the UE receives an UL grant or an AUL-DFI indicatesfeedback for one or more previous transmissions {T₀, . . . , T_(n)}using first Type channel access procedure, from the startsubframe(s)/slot(s)/mini-slot(s)/TTI(s) of the previous transmission(s)of which, N or more subframes/slots/mini-slots/TTIs have elapsed andneither UL grant nor AUL-DFI was received, where N=max (ContentionWindow Size adjustment timer X, T_(i) burst length+1) if X >0 and N=0otherwise, the UE may recompute CW_(p) as follows: the UE reverts CW_(p)to the value used to transmit at n_(T0) using first Type channel accessprocedure; the UE updates CW_(p) sequentially in the order of thetransmission {T₀, . . . , T_(n)}. If the NDI value for at least one HARQprocess associated with HARQ_ID_ref is toggled, or if the HARQ-ACKvalue(s) for at least one of the HARQ processes associated withHARQ_ID_ref received in the earliest AUL-DFI after n_(Ti)+3 indicatesACK. For every priority class p∈{1,2,3,4} set CW_(p)=CW_(min,p).Otherwise, increase CW_(p) for every priority class p∈{1,2,3,4} to thenext higher allowed value.

If the UE transmits transmissions using first Type channel accessprocedure before N subframes/slots/mini-slots/TTIs have elapsed from thestart of previous UL transmission burst using first Type channel accessprocedure and neither UL grant nor AUL-DFI is received, the CW_(p) maybe unchanged.

In an example, the HARQ_ID_ref may be the HARQ process ID of UL-SCH inreference subframe/slot/mini-slot/TTI n_(ref). The referencesubframe/slot/mini-slot/TTI n_(ref) may be determined as follows: If theUE receives an UL grant or an AUL-DFI in subframe/slot/mini-slot/TTIn_(g), subframe/slot/mini-slot/TTI n_(w) may be the most recentsubframe/slot/mini-slot/TTI before subframe/slot/mini-slot/TTI n_(g)−3in which the UE has transmitted UL-SCH using first Type channel accessprocedure. In an example, if the UE transmits transmissions includingUL-SCH without gaps starting with subframe/slot/mini-slot/TTI n₀ and insubframes/slots/mini-slots/TTIs n₀, n₁, . . . , n_(w) and the UL-SCH insubframe/slot/mini-slot/TTI n₀ is not PUSCH Mode 1 that starts in thesecond slot of the subframe/slot/mini-slot/TTI, referencesubframe/slot/mini-slot/TTI n_(ref) may be subframe/slot/mini-slot/TTIn₀. In an example, if the UE transmits transmissions including a firstPUSCH Mode without gaps starting with second slot ofsubframe/slot/mini-slot/TTI n₀ and in subframe/slot/mini-slot/TTI n₀,n₁, . . . , n_(w) and the, reference subframe/slot/mini-slot/TTI n_(ref)is subframe/slot/mini-slot/TTI n₀ and n₁, otherwise, referencesubframe/slot/mini-slot/TTI n_(ref) may be subframe/slot/mini-slot/TTI

In an example, HARQ_ID_ref may be the HARQ process ID of UL-SCH inreference subframe/slot/mini-slot/TTI n_(Ti). The referencesubframe/slot/mini-slot/TTI n_(Ti) may be determined as the startsubframe/slot/mini-slot/TTI of a transmission T_(i) using a first Typechannel access procedure and of which, N subframes/slots/mini-slots/TTIshave elapsed and neither UL grant nor AUL-DFI was received.

In an example, if the AUL-DFI with a first DCI format is indicated to aUE that is activated with AUL transmission and a second transmissionmode is configured for the UE for grant-based uplink transmissions, thespatial HARQ-ACK bundling may be performed by logical OR operationacross multiple codewords for the HARQ process not configured forautonomous UL transmission.

In an example, if CW_(p) changes during an ongoing channel accessprocedure, the UE may draw a counter N_(init) and applies it to theongoing channel access procedure.

In an example, the UE may keep the value of CW_(p) unchanged for everypriority class p∈{1,2,3,4}, if the UE scheduled to transmittransmissions without gaps including PUSCH in a set ofsubframes/slots/mini-slots/TTIs n₀, n₁, . . . , n_(w-1) using a firstType channel access procedure, and if the UE is not able to transmit anytransmission including PUSCH in the set ofsubframes/slots/mini-slots/TTIs.

In an example, the UE may keep the value of CW_(p) for every priorityclass p∈{1,2,3,4} the same as that for the last scheduled transmissionincluding PUSCH using first Type channel access procedure, if thereference subframe/slot/mini-slot/TTI for the last scheduledtransmission is also n_(ref).

In an example, if CW_(p)=CW_(max,p), the next higher allowed value foradjusting CW_(p) is CW_(max,p).

In an example, if the CW_(p)=CW_(max,p) is consecutively used K timesfor generation of N_(init),CW_(p) may be reset to CW_(min,p) for thatpriority class p for which CW_(p)=CW_(max,p) is consecutively used Ktimes for generation of N_(init). In an example, K may be selected by UEfrom the set of values {1, 2, . . . , 8} for a priority classp∈{1,2,3,4}.

In an example, a UE accessing a carrier on which LAA Scell(s)transmission(s) are performed, may set the energy detection threshold(X_(Thresh)) to be less than or equal to the maximum energy detectionthreshold X_(Tmesh_max).

In an example, if the UE is configured with higher layer parametermaxEnergyDetectionThreshold, X_(Thresh_max) may be set equal to thevalue signalled by the higher layer parameter. Otherwise, the UE maydetermine X′_(Thresh_max) according to a first procedure for determiningenergy detection threshold. In an example, if the UE is configured withhigher layer parameter energyDetectionThresholdOffset, X_(Thresh_max)may be set by adjusting X′_(Thresh_max) according to the offset valuesignalled by the higher layer parameter. Otherwise, the UE may setX_(Thresh_max)=X′_(Thresh_max).

In an example, the first procedure for determining the energy detectionthreshold may be as follows: if the higher layer parameterabsenceOfAnyOtherTechnology indicates TRUE,

$X_{{Thresh}\_\max}^{\prime} = {\min\begin{Bmatrix}T_{\max} \\X_{r}\end{Bmatrix}}$where X_(r) is Maximum energy detection threshold defined by regulatoryrequirements in dBm when such requirements are defined, otherwiseX_(r)=T_(max).

${Otherwise},{X^{\prime}\max\begin{Bmatrix}{\left. {{- 72} + {{10 \cdot \log}\; 10\left( {{{{BW}{MHz}}/20}\mspace{14mu}{MHz}} \right)}}\rightleftarrows{dBm} \right.,} \\{\min\begin{Bmatrix}{T_{\max},} \\{{TA}\left( {P_{H} + {10 \cdot}} \right.} \\\left. {\log\; 10\left( {{{BWMHz}/20}\mspace{14mu}{MHz}} \right)}\rightleftarrows{- P_{TX}} \right)_{\max}\end{Bmatrix}}\end{Bmatrix}_{{Thres}\_\max}},$where T_(A)=10 dB, P_(H)=23 dBm; P_(TX) may be the set to the value ofPCMAX_H,c; TdBm log 1 (3.16228·10⁻⁸ (mW/MHz)·BWMHz (MHz))_(max); BWMHzmay be the single carrier bandwidth in MHz.

In an example, an LBT operation may follow a back-off algorithm based onCWS (contention window size) management. In an example, CWS update forDL/UL may be based on the decoding results of TB(s) in referencesubframe(s). In an example, separate HARQ operation may be possible fordifferent cpde blocks (CBs) for a same TB. In an example, CWS managementmay be based on CBG operation.

In an example, CWS update for DL/UL may be based on the decoding resultsof TB(s) in reference subframe(s) and the minimum(/maximum) timing gapbetween a reference subframe and the corresponding CWS update timing maybe defined. In an example, base station scheduler may adapt timingrelationship between PDSCH and UL HARQ feedback, between PUSCHtransmission and retransmission, and so on. In an example, UEs mayreport different capabilities on those timing relationships. In anexample, flexible DL/UL scheduling timing and the related UEcapabilities may impact CWS management.

In an example, a UE may be configured with multiple DL/UL BWPs for acarrier. In an example, a base station may dynamically switch the UE'soperating BWP by DCI and/or the BW may switch based on a BWP inactivitytimer. The impact of BWP switching on CWS management may be considered.

In an example, to improve UL coverage (e.g., for high frequencyscenarios) supplementary uplink (e.g., SUL) may be configured. In anexample, with SUL, a UE may be configured with two or more UL carriersfor one DL of the same cell. An example scenario is shown in FIG. 19.

In an example, in case of a Supplementary Uplink (e.g., SUL), a UE maybe configured with two or more UL carriers for one DL of the same cell.In an example, the uplink transmissions on those two UL carriers may becontrolled by the network to avoid overlapping PUSCH/PUCCH transmissionsin time. In an example, overlapping transmissions on PUSCH may beavoided through scheduling. In an example, overlapping transmissions onPUCCH may be avoided through configuration. In an example, PUCCH may beconfigured for one of the 2 UL carriers of the cell. In an example,initial access may be supported in each of the uplink carriers

In an example, a Supplementary UL (SUL) carrier may be configured as acomplement to the normal UL (NUL) carrier. Switching between the NULcarrier and the SUL carrier may indicate that the UL transmissions movefrom a PUSCH on one carrier to another carrier. In an example, theswitching the uplink carrier may be done via an indication in DCI. In anexample, if a MAC entity receives an uplink grant indicating a SULswitch while a Random Access procedure is ongoing, the MAC entity mayignore the UL grant.

In an example, a Serving Cell configured with supplementaryUplink maybelong to a single TAG.

In an example, DCI format 0_0 may be used for the scheduling of PUSCH inone cell. In an example, the DCI format 0_0 may comprise a UL/SULindicator field. The UL/SUL indicator field may comprise 1 bit if thecell has two UL carriers and the number of bits for DCI format 1_0before padding is larger than the number of bits for DCI format 0_0before padding. Otherwise, the field may not be present (e.g., may havezero bits). In an example, the UL/SUL indicator field, if present, maylocate in the last bit position of DCI format 0_0, after the paddingbit(s). In an example, a value of zero may indicate thenon-supplementary uplink and a value of one may indicate thesupplementary uplink.

In an example, if a UE is configured with two UL carriers in a servingcell, a same value for timing offset calculation may apply to bothcarriers. In an example, the value of timing offset calculation may bedetermined from the non-supplementary UL carrier.

In an example, for a serving cell in a set of serving cells, the UE maybe provided by a first reference subcarrier spacing parameter and, whena supplementary UL carrier is configured for the serving cell, a secondreference subcarrier spacing by higher layer parameter for thesupplementary UL carrier.

In an example, an initial active DL BWP may be defined by a location andnumber of contiguous PRBs, a subcarrier spacing, and a cyclic prefix,for the control resource set for Type0-PDCCH common search space. Foroperation on the primary cell or on a secondary cell, a UE may providedan initial active UL BWP by higher layer parameter initialuplinkBWP. Ifthe UE is configured with a supplementary carrier, the UE may beprovided an initial UL BWP on the supplementary carrier by higher layerparameter initialUplinkBWP in supplementaryUplink.

In an example, if a UE is configured by higher layer parameterfirstActiveDownlinkBWP-Id a first active DL BWP and by higher layerparameter firstActiveUplinkBWP-Id a first active UL BWP on a secondarycell or supplementary carrier, the UE uses the indicated DL BWP and theindicated UL BWP on the secondary cell as the respective first active DLBWP and first active UL BWP on the secondary cell or supplementarycarrier.

In an example, a Serving Cell may be configured with one or multipleBWPs, and the maximum number of BWP per Serving Cell may be specified.In an example, a BWP switching for a Serving Cell may be used toactivate an inactive BWP and deactivate an active BWP at a time. The BWPswitching may be controlled by the PDCCH indicating a downlinkassignment or an uplink grant and/or by the bwp-InactivityTimer and/orby RRC signalling and/or or by the MAC entity itself upon initiation ofRandom Access procedure.

In an example, upon/in response to addition of SpCell or activation ofan SCell, the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Idand firstActiveUplinkBWP-Id respectively may be active without receivingPDCCH indicating a downlink assignment or an uplink grant. The activeBWP for a Serving Cell may be indicated by either RRC or PDCCH. Forunpaired spectrum, a DL BWP may be paired with a UL BWP, and BWPswitching may be common for both UL and DL.

In an example, for each activated Serving Cell configured with a BWP, ifa BWP is activated the MAC entity may transmit on UL-SCH on the BWPand/or the MAC entity may transmit on RACH on the BWP and/or the MACentity may monitor the PDCCH on the BWP and/or the MAC entity maytransmit PUCCH on the BWP and/or the MAC entity may transmit SRS on theBWP and/or the MAC entity may receive DL-SCH on the BWP and/or theMACentity may re-)initialize any suspended configured uplink grants ofconfigured grant Type 1 on the active BWP according to the storedconfiguration, if any, and to start in a symbol.

In an example, for each activated Serving Cell configured with a BWP, ifa BWP is deactivated the MAC entity may not transmit on UL-SCH on theBWP and/or the MAC entity may not transmit on RACH on the BWP and/or theMAC entity may not monitor the PDCCH on the BWP and/or the MAC entitymay not transmit PUCCH on the BWP and/or the MAC entity may not reportCSI for the BWP and/or the MAC entity may not transmit SRS on the BWPand/or the MAC entity may not receive DL-SCH on the BWP and/or the MACentity may clear any configured downlink assignment and configureduplink grant of configured grant Type 2 on the BWP and/or the MAC entitymay suspend any configured uplink grant of configured grant Type 1 onthe inactive BWP.

In an example, upon/in response to initiation of the Random Accessprocedure on a Serving Cell, if PRACH occasions are not configured forthe active UL BWP of the serving cell, the MAC entity may switch theactive UL BWP of the serving cell to BWP of the serving cell indicatedby initialUplinkBWP. In an example, upon/in response to initiation ofthe Random Access procedure on a Serving Cell, if PRACH occasions arenot configured for the active UL BWP, if the serving cell is a SpCell(e.g., PCell or PSCell), the MAC entity may switch the active DL BWP toBWP indicated by initialDownlinkBWP.

In an example, upon/in response to initiation of the Random Accessprocedure on a Serving Cell, if PRACH occasions are configured for theactive UL BWP of the serving cell, if the Serving Cell is a SpCell andif the active DL BWP does not have the same bwp-Id as the active UL BWP,the MAC entity may switch the active DL BWP to the DL BWP with the samebwp-Id as the active UL BWP.

In an example, upon/in response to initiation of the Random Accessprocedure on a Serving Cell, the MAC entity may perform the RandomAccess procedure on the active DL BWP of SpCell and active UL BWP ofthis Serving Cell.

In an example, if the MAC entity receives a PDCCH for BWP switching of aserving cell, and if there is no ongoing Random Access procedureassociated with this Serving Cell and if the ongoing Random Accessprocedure associated with this Serving Cell is successfully completedupon reception of this PDCCH addressed to C-RNTI, the MAC entity mayperform BWP switching to a BWP indicated by the PDCCH.

In an example, if the MAC entity receives a PDCCH for BWP switching fora Serving Cell while a Random Access procedure associated with thatServing Cell is ongoing in the MAC entity, it may be up to UEimplementation whether to switch BWP or ignore the PDCCH for BWPswitching, except for the PDCCH reception for BWP switching addressed tothe C-RNTI for successful Random Access procedure completion in whichcase the UE may perform BWP switching to a BWP indicated by the PDCCH.In an example, upon/in response to reception of the PDCCH for BWPswitching other than successful contention resolution, if the MAC entitydecides to perform BWP switching, the MAC entity may stop the ongoingRandom Access procedure and initiate a Random Access procedure on thenew activated BWP; if the MAC decides to ignore the PDCCH for BWPswitching, the MAC entity may continue with the ongoing Random Accessprocedure on the active BWP.

In an example, if the bwp-InactivityTimer is configured, if thedefaultDownlinkBWP is configured, and the active DL BWP is not the BWPindicated by the defaultDownlinkBWP; or if the defaultDownlinkBWP is notconfigured, and the active DL BWP is not the initialDownlinkBWP: if aPDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment oruplink grant is received on the active BWP; or if a PDCCH addressed toC-RNTI or CS-RNTI indicating downlink assignment or uplink grant isreceived for the active BWP; or if a MAC PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment:if there is no ongoing random access procedure associated with thisServing Cell; or if the ongoing Random Access procedure associated withthis Serving Cell is successfully completed upon reception of this PDCCHaddressed to C-RNTI, the MAC entity may, for each activated ServingCell, start or restart the bwp-InactivityTimer associated with theactive DL BWP.

In an example, if the bwp-InactivityTimer is configured, if thedefaultDownlinkBWP is configured, and the active DL BWP is not the BWPindicated by the defaultDownlinkBWP; or if the defaultDownlinkBWP is notconfigured, and the active DL BWP is not the initialDownlinkBWP and if aPDCCH for BWP switching is received on the active DL BWP, and the MACentity switches the active BWP, the MAC entity may, for each activatedServing Cell, start or restart the bwp-InactivityTimer associated withthe active DL BWP.

In an example, if the bwp-InactivityTimer is configured, if thedefaultDownlinkBWP is configured, and the active DL BWP is not the BWPindicated by the defaultDownlinkBWP; or if the defaultDownlinkBWP is notconfigured, and the active DL BWP is not the initialDownlinkBWP and ifRandom Access procedure is initiated on this Serving Cell, the MACentity may stop the bwp-InactivityTimer associated with the active DLBWP of this Serving Cell, if running; and if the Serving Cell is SCell:the MAC entity may stop the bwp-InactivityTimer associated with theactive DL BWP of SpCell, if running.

In an example, if the bwp-InactivityTimer is configured, if thedefaultDownlinkBWP is configured, and the active DL BWP is not the BWPindicated by the defaultDownlinkBWP; or if the defaultDownlinkBWP is notconfigured, and the active DL BWP is not the initialDownlinkBWP, if thebwp-InactivityTimer associated with the active DL BWP expires: if thedefaultDownlinkBWP is configured: the MAC entity may perform BWPswitching to a BWP indicated by the defaultDownlinkBWP.

In an example, if the bwp-InactivityTimer is configured, if thedefaultDownlinkBWP is configured, and the active DL BWP is not the BWPindicated by the defaultDownlinkBWP; or if the defaultDownlinkBWP is notconfigured, and the active DL BWP is not the initialDownlinkBWP, if thebwp-InactivityTimer associated with the active DL BWP expires: if thedefaultDownlinkBWP is not configured: the MAC entity may perform BWPswitching the initialDownlinkBWP.

In an example embodiment, as shown in FIG. 20, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise RRC messages. In an example, the oneor more messages may comprise first configuration parameters of alicensed cell. In an example, the one or more messages may comprisesecond configuration parameters of an unlicensed cell. The firstconfiguration parameters may indicate first bandwidth part configurationparameters of a first bandwidth part and a second bandwidth part of thelicensed cell. The second configuration parameters may indicate secondbandwidth part configuration parameters of a third bandwidth part and afourth bandwidth part of the unlicensed cell.

In an example, the wireless device may receive a first downlink controlinformation indicating switching from the first bandwidth part to thesecond bandwidth part. In an example, the first downlink controlinformation may indicate a first uplink grant for the second bandwidthpart. In an example, the first downlink control information may indicatetransmission parameters (e.g., radio resources, HARQ related parameterssuch as HARQ ID, NDI, RV, power control commands, etc.) for transmissionof one or more transport blocks via the second bandwidth part. In anexample, the first downlink control information may comprise a field(e.g., bandwidth part ID field) indicating an ID of the second bandwidthpart. In an example, the first downlink control information may betransmitted as part of a random access process. In an example, the firstdownlink control information may be transmitted as message 2 (e.g., RAR)in a random access process. In an example, the first downlink controlinformation may be transmitted as message 4 (e.g., contentionresolution) in a random access process. In an example, the wirelessdevice may switch from the first bandwidth part to the second bandwidthpart in response to receiving the first downlink control information. Inan example, the wireless device may switch from the first bandwidth partto the second bandwidth part, without transmitting a confirmation, inresponse to receiving the first downlink control information.

In an example, the wireless device may receive a second downlink controlinformation indicating switching from the third bandwidth part to thefourth bandwidth part. Example scenarios are shown in FIG. 20 and FIG.21. In an example, the second downlink control information may indicatea second uplink grant for the fourth bandwidth part. In an example, thesecond downlink control information may indicate transmission parameters(e.g., radio resources, HARQ related parameters such as HARQ ID, NDI,RV, power control commands, etc.) for transmission of one or moretransport blocks on the fourth bandwidth part. In an example, the seconddownlink control information may comprise a field (e.g., a bandwidthpart ID field) indicating an ID of the fourth bandwidth part. In anexample, the second downlink control information may be transmitted aspart of a random access process. In an example, the second downlinkcontrol information may be transmitted as message 2 (e.g., RAR) in arandom access process. In an example, the second downlink controlinformation may be transmitted as message 4 (e.g., contentionresolution) in a random access process. The wireless device may, inresponse to receiving the second downlink control information, switchfrom the third bandwidth part to the fourth bandwidth part. In anexample, the wireless device may, in response to receiving the seconddownlink control information, switch from the third bandwidth part tothe fourth bandwidth part and transmit a confirmation to the basestation.

In an example, the confirmation may be transmitted via a control element(e.g., MAC control element). In an example, the base station maytransmit one or more messages comprising configuration parameters of theMAC control element indicating the confirmation for BWP switching. In anexample, the MAC control element indicating the confirmation for BWPswitching may be associated with a logical channel identifier (LCID). Inan example, the LCID may have a pre-configured value. In an example, theMAC CE may indicate that switching is from the third BWP and/or theswitching changes the active bandwidth part to the fourth BWP. In anexample, the payload of the MAC CE may indicate the third and/or thefourth bandwidth part. In an example, the payload of the MAC CE maycomprise an ID of the third BWP and/or an ID of the fourth BWP. In anexample, the ID of the third BWP and/or the ID of the fourth BWP may beRRC configured. In an example, the MAC CE may comprise zero SDU/payloadand the LCID may indicate that the MAC CE is for BWP switchingconfirmation.

In an example, the confirmation may be transmitted via uplink controlchannel (e.g., PUCCH) and/or may be multiplexed via uplink sharedchannel (e.g., PUSCH). In an example, the confirmation may be an uplinkcontrol information. In an example, the confirmation may be anacknowledgement (e.g., ACK/NACK) and may be transmitted via PUCCH orPUSCH. In an example, the acknowledgement may indicate (e.g., explicitlyor implicitly) that the wireless device received the DCI indicatingswitching from the third BWP to the fourth BWP or that the wirelessdevice has switched form the third BWP to the fourth BWP. In an example,a resource (e.g., the PUCCH resource) used for transmission of theacknowledgement may indicate that the wireless device received the DCIindicating switching from the third BWP to the fourth BWP or that thewireless device has switched form the third BWP to the fourth BWP.

In an example embodiment as shown in FIG. 22, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise RRC messages. In an example, the oneor more messages may comprise first configuration parameters of alicensed cell. In an example, the one or more messages may comprisesecond configuration parameters of an unlicensed cell. The firstconfiguration parameters may indicate first bandwidth part configurationparameters of a first bandwidth part and a second bandwidth part of thelicensed cell. The second configuration parameters may indicate secondbandwidth part configuration parameters of a third bandwidth part and afourth bandwidth part of the unlicensed cell.

In an example, the wireless device may receive a first downlink controlinformation. The first downlink control information may be transmittedas a PDCCH order. The first downlink control information may indicateinitiating a random access procedure on the first bandwidth part. Thewireless device may switch to the second bandwidth part in response toreceiving the first downlink control information and no random accessoccasion/resource being configured on the first bandwidth part. In anexample, the first downlink control information may have a DCI format1_0. In an example, the first downlink control information may indicateat least one of a random access preamble index, uplink carrier (e.g.,NUL/SUL) indicator, PRACH mask index for initiating a random accessprocess. In an example, the random access preamble indicated by thefirst downlink control information may be a random access preamble in aplurality of random access preambles. In an example, uplink carrierindicator may indicate one of a normal uplink carrier or a supplementaryuplink carrier. In an example, the uplink carrier indicator may indicatethe UL carrier in a cell to transmit the PRACH in response to the valueof the random access preamble index not being all zeros and the wirelessdevice being configured with SUL in the cell, otherwise the UL carrierfield may be reserved. In an example, the PRACH mask index may indicatea RACH occasion associated with the SS/PBCH indicated by “SS/PBCH index”for PACH transmission in response to the PRACH mask index being allzeros, otherwise the PRACH mask index field may be reserved. In anexample, the first downlink control information may comprise a fieldindicating an identifier of the first bandwidth part.

In an example, the wireless device may receive a second downlink controlinformation. The second downlink control information may be transmittedas a PDCCH order. Example scenarios are shown in FIG. 22 and FIG. 23.The second downlink control information may indicate initiating a randomaccess procedure on the third bandwidth part. In an example, the seconddownlink control information may have a DCI format 1_0. In an example,the second downlink control information may indicate at least one of arandom access preamble index, uplink carrier (e.g., NUL/SUL) indicator,PRACH mask index for initiating a random access process. In an example,the random access preamble indicated by the second downlink controlinformation may be a random access preamble in a plurality of randomaccess preambles. In an example, uplink carrier indicator may indicateone of a normal uplink carrier (NUL) and a supplementary uplink carrier(SUL). In an example, the uplink carrier indicator may indicate the ULcarrier in a cell to transmit the PRACH in response to the value of therandom access preamble index not being all zeros and the wireless devicebeing configured with SUL in the cell, otherwise the UL carrier fieldmay be reserved. In an example, the PRACH mask index may indicate a RACHoccasion associated with the SS/PBCH indicated by “SS/PBCH index” forPACH transmission in response to the PRACH mask index being all zeros,otherwise the PRACH mask index field may be reserved. In an example, thesecond downlink control information may comprise a field indicating anidentifier of the third bandwidth part. The wireless device may switchto the fourth bandwidth part in response to receiving the seconddownlink control information and no random access occasion/resourcebeing configured on the third bandwidth part. The wireless device maytransmit a confirmation in response to switching to the fourth bandwidthpart.

In an example, the confirmation may be transmitted via a control element(e.g., MAC control element). In an example, the base station maytransmit one or more messages comprising configuration parameters of theMAC control element indicating the confirmation for BWP switching. In anexample, the MAC control element indicating the confirmation for BWPswitching may be associated with a logical channel identifier (LCID). Inan example, the LCID may have a pre-configured value. In an example, theMAC CE may indicate that switching is from the third BWP and/or theswitching changes the active bandwidth part to the fourth BWP. In anexample, the payload of the MAC CE may indicate the third and/or thefourth bandwidth part. In an example, the payload of the MAC CE maycomprise an ID of the third BWP and/or an ID of the fourth BWP. In anexample, the ID of the third BWP and/or the ID of the fourth BWP may beRRC configured. In an example, the MAC CE may comprise zero SDU/payloadand the LCID may indicate that the MAC CE is for BWP switchingconfirmation.

In an example, the confirmation may be transmitted via uplink controlchannel (e.g., PUCCH) and/or may be multiplexed via uplink sharedchannel (e.g., PUSCH). In an example, the confirmation may be an uplinkcontrol information. In an example, the confirmation may be anacknowledgement (e.g., ACK/NACK) and may be transmitted via PUCCH orPUSCH. In an example, the acknowledgement may indicate (e.g., explicitlyor implicitly) that the wireless device received the DCI indicatingswitching from the third BWP to the fourth BWP or that the wirelessdevice has switched form the third BWP to the fourth BWP. In an example,a resource (e.g., the PUCCH resource) used for transmission of theacknowledgement may indicate that the wireless device received the DCIindicating switching from the third BWP to the fourth BWP or that thewireless device has switched form the third BWP to the fourth BWP.

In an example embodiment as shown in FIG. 24, a wireless device mayreceive first configuration parameters of a first uplink carrier and asecond uplink carrier of a first cell. In an example, the second uplinkcarrier of the first cell may be licensed. In an example, the firstuplink carrier of the first cell may be licensed or unlicensed and thesecond uplink carrier of the first cell may be licensed. In an example,the wireless device may receive second configuration parameters of athird uplink carrier and the fourth uplink carrier of a second cell. Inan example, the fourth uplink carrier of the second cell may beunlicensed. In an example, the fourth uplink carrier of the second cellmay be unlicensed and the third uplink carrier of the second cell may belicensed or unlicensed.

In an example, the wireless device may receive a first downlink controlinformation indicating switching (moving) from the first uplink carrierto the second uplink carrier. In an example, a value of an uplinkcarrier indicator field in the first downlink control information mayindicate the second uplink carrier while the first uplink carrier is anactive uplink carrier of the first cell. In an example, the first uplinkcarrier or the second uplink carrier may be a normal uplink carrier or asupplementary uplink carrier. In an example, the first downlink controlinformation may indicate a first uplink grant in the second uplinkcarrier. The first uplink grant may indicate transmission parameters fortransmission of one or more transport blocks in the second uplinkcarrier. The transmission parameters may comprise one or more of radioresources for transmission of the one or more transport block, HARQrelated parameters (e.g., HARQ ID, NDI, RV, etc.), power control relatedparameters, etc.

In an example, the wireless device may switch from the first uplinkcarrier to the second uplink carrier in response to receiving the firstdownlink control information. In an example, the wireless device mayswitch from the first uplink carrier to the second uplink carrier,without transmitting a confirmation/acknowledgement in response toreceiving the first downlink control information.

In an example, the wireless device may receive a second downlink controlinformation indicating switching (moving) from the third uplink carrierto the fourth uplink carrier. Example scenarios are shown in FIG. 24 andFIG. 25. In an example, a value of an uplink carrier indicator field inthe second downlink control information may indicate the fourth uplinkcarrier while the third uplink carrier is an active uplink carrier ofthe second cell. In an example, the third uplink carrier or the fourthuplink carrier may be a normal uplink carrier or a supplementary uplinkcarrier. In an example, the second downlink control information mayindicate a second uplink grant in the fourth uplink carrier. The seconduplink grant may indicate transmission parameters for transmission ofone or more transport blocks in the fourth uplink carrier. Thetransmission parameters may comprise one or more of radio resources fortransmission of the one or more transport block, HARQ related parameters(e.g., HARQ ID, NDI, RV, etc.), power control related parameters, etc.

In an example, in response to receiving the second downlink controlinformation, the wireless device may switch from the third uplinkcarrier to the fourth uplink carrier. In an example, in response toreceiving the second downlink control information, the wireless devicemay transmit a conformation/acknowledgement. In an example, in responseto receiving the second downlink control information, the wirelessdevice may switch from the third uplink carrier to the fourth uplinkcarrier and the wireless device may transmit aconformation/acknowledgement.

In an example, the confirmation may be transmitted via a control element(e.g., MAC control element). In an example, the base station maytransmit one or more messages comprising configuration parameters of theMAC control element indicating the confirmation for uplink carrierswitching. In an example, the MAC control element indicating theconfirmation for uplink carrier switching may be associated with alogical channel identifier (LCID). In an example, the LCID may have apre-configured value. In an example, the MAC CE may indicate thatswitching is from the third uplink carrier and/or the switching changesthe active uplink carrier to the fourth uplink carrier. In an example,the payload of the MAC CE may indicate the third and/or the fourthuplink carrier. In an example, the payload of the MAC CE may comprise anID of the third uplink carrier and/or an ID of the fourth uplinkcarrier. In an example, the ID of the third uplink carrier and/or the IDof the fourth uplink carrier may be RRC configured. In an example, theMAC CE may comprise zero SDU/payload and the LCID may indicate that theMAC CE is for uplink carrier switching confirmation.

In an example, the confirmation may be transmitted via uplink controlchannel (e.g., PUCCH) and/or may be multiplexed via uplink sharedchannel (e.g., PUSCH). In an example, the confirmation may be an uplinkcontrol information. In an example, the confirmation may be anacknowledgement (e.g., ACK/NACK) and may be transmitted via PUCCH orPUSCH. In an example, the acknowledgement may indicate (e.g., explicitlyor implicitly) that the wireless device received the DCI indicatingswitching from the third uplink carrier to the fourth uplink carrier orthat the wireless device has switched form the third uplink carrier tothe fourth uplink carrier. In an example, a resource (e.g., the PUCCHresource) used for transmission of the acknowledgement may indicate thatthe wireless device received the DCI indicating switching from the thirduplink carrier to the fourth uplink carrier or that the wireless devicehas switched form the third uplink carrier to the fourth uplink carrier.

FIG. 26 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 2610, a wireless device may receive firstconfiguration parameters of a first bandwidth part and a secondbandwidth part of a licensed cell; and second configuration parametersof a third bandwidth part and a fourth bandwidth part of an unlicensedcell. At 2620, a determination may be made that a first downlink controlinformation indicating switching from the first bandwidth part to thesecond bandwidth part as an active bandwidth part is received. At 2630,based on the receiving the first downlink control information, thewireless device may switch from the first bandwidth part to the secondbandwidth part; and not transmit a confirmation. At 2640, adetermination may be made that a second downlink control informationindicating switching from the third bandwidth part to the fourthbandwidth part as an active bandwidth part is received. At 2650, basedon the receiving the second downlink control information, the wirelessdevice may switch from the third bandwidth part to the fourth bandwidthpart; and transmit a confirmation.

FIG. 27 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 2710, a wireless device may receive firstconfiguration parameters of a first uplink carrier and a second uplinkcarrier of a licensed cell; and second configuration parameters of athird uplink carrier and a fourth uplink carrier of an unlicensed cell.At 2720, a determination may be made that a first downlink controlinformation indicating switching from the first uplink carrier to thesecond uplink carrier is received. At 2730, based on the receiving thefirst downlink control information, the wireless device may switch fromthe first uplink carrier to the second uplink carrier; and not transmita confirmation. At 2740, a determination may be made that a seconddownlink control information indicating switching from the third uplinkcarrier to the fourth uplink carrier is received. At 2750, based on thereceiving the second downlink control information, the wireless devicemay switch from the third uplink carrier to the fourth uplink carrier;and transmit a confirmation.

FIG. 28 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 2810, a base station may transmit firstconfiguration parameters of a first bandwidth part and a secondbandwidth part of a licensed cell; and second configuration parametersof a third bandwidth part and a fourth bandwidth part of an unlicensedcell. At 2820, a determination may be made that a first downlink controlinformation indicating switching from the first bandwidth part to thesecond bandwidth part as an active bandwidth part is transmitted. At2830, based on the transmitting the first downlink control information,the base station may switch from the first bandwidth part to the secondbandwidth part; and not monitor for a confirmation. At 2840, adetermination may be made that a second downlink control informationindicating switching from the third bandwidth part to the fourthbandwidth part as an active bandwidth part is transmitted. At 2850,based on the transmitting the second downlink control information, thebase station may switch from the third bandwidth part to the fourthbandwidth part; and monitor for a confirmation.

FIG. 29 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 2910, a base station may transmit firstconfiguration parameters of a first uplink carrier and a second uplinkcarrier of a licensed cell; and second configuration parameters of athird uplink carrier and a fourth uplink carrier of an unlicensed cell.At 2920, a determination may be made that a first downlink controlinformation indicating switching from the first uplink carrier to thesecond uplink carrier is transmitted. At 2930, based on the transmittingthe first downlink control information, the base station may switch fromthe first uplink carrier to the second uplink carrier; and not monitorfor a confirmation. At 2940, a determination may be made that a seconddownlink control information indicating switching from the third uplinkcarrier to the fourth uplink carrier is transmitted. At 2950, based onthe transmitting the second downlink control information, the basestation may switch from the third uplink carrier to the fourth uplinkcarrier; and monitor for a confirmation.

According to an example embodiment, a wireless device may receive firstconfiguration parameters of a first bandwidth part and a secondbandwidth part of a licensed cell. The wireless device may furtherreceive second configuration parameters of a third bandwidth part and afourth bandwidth part of an unlicensed cell. A first downlink controlinformation indicating switching from the first bandwidth part to thesecond bandwidth part as an active bandwidth part may be received. Asecond downlink control information indicating switching from the thirdbandwidth part to the fourth bandwidth part as an active bandwidth partmay be received. Based on the receiving the first downlink controlinformation, the wireless device may switch from the first bandwidthpart to the second bandwidth part and not transmit a confirmation. Basedon the receiving the second downlink control information, the wirelessdevice may switch from the third bandwidth part to the fourth bandwidthpart and transmit a confirmation.

According to an example embodiment, the confirmation may be a mediumaccess control (MAC) control element. According to an exampleembodiment, the transmitting the confirmation may be via an uplink datachannel According to an example embodiment, the confirmation maycomprise a first identifier of the third bandwidth part and a secondidentifier of the fourth bandwidth part. According to an exampleembodiment, the first downlink control information may indicate anuplink grant for transmission of one or more transport blocks via thesecond bandwidth part. According to an example embodiment, the firstdownlink control information may indicate an order for a random accessprocedure.

According to an example embodiment, the confirmation may be anacknowledgement. According to an example embodiment, the transmittingthe confirmation may be via an uplink control channel. According to anexample embodiment, the transmitting the confirmation may be via anuplink data channel.

According to an example embodiment, the transmitting the confirmationmay be via an uplink control channel According to an example embodiment,the transmitting the confirmation may be via an uplink data channelAccording to an example embodiment, the confirmation may comprise afirst identifier of the third bandwidth part and a second identifier ofthe fourth bandwidth part. According to an example embodiment, the firstdownlink control information may indicate an uplink grant fortransmission of one or more transport blocks via the second bandwidthpart. According to an example embodiment, the first downlink controlinformation may indicate an order for a random access procedure.

According to an example embodiment, the second downlink controlinformation may indicate an uplink grant for transmission of one or moretransport blocks via the fourth bandwidth part. According to an exampleembodiment, the confirmation may be a medium access control (MAC)control element. According to an example embodiment, the confirmationmay be an acknowledgement.

According to an example embodiment, the second downlink controlinformation may indicate an order for a random access procedure.According to an example embodiment, the confirmation may be a mediumaccess control (MAC) control element. According to an exampleembodiment, the confirmation may be an acknowledgement.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of base stations or a plurality ofwireless devices in a coverage area that may not comply with thedisclosed methods, for example, because those wireless devices or basestations perform based on older releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more (or at leastone) message(s) comprise a plurality of parameters, it implies that aparameter in the plurality of parameters is in at least one of the oneor more messages, but does not have to be in each of the one or moremessages. In an example embodiment, when one or more (or at least one)message(s) indicate a value, event and/or condition, it implies that thevalue, event and/or condition is indicated by at least one of the one ormore messages, but does not have to be indicated by each of the one ormore messages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (i.e.hardware with a biological element) or a combination thereof, all ofwhich may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device. Theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

The invention claimed is:
 1. A method comprising: receiving, by awireless device: first configuration parameters of a first bandwidthpart and a second bandwidth part of a licensed cell; and secondconfiguration parameters of a third bandwidth part and a fourthbandwidth part of an unlicensed cell; receiving a first downlink controlinformation indicating switching from the first bandwidth part to thesecond bandwidth part as an active bandwidth part; receiving a seconddownlink control information indicating switching from the thirdbandwidth part to the fourth bandwidth part as an active bandwidth part;determining whether to transmit a confirmation for bandwidth partswitching based on the bandwidth part switching being for the licensedcell or the unlicensed cell; based on determining that the firstdownlink control information is for the licensed cell: switching fromthe first bandwidth part to the second bandwidth part; and nottransmitting a confirmation; and based on determining that the seconddownlink control information is for the unlicensed cell: switching fromthe third bandwidth part to the fourth bandwidth part; and transmittinga confirmation.
 2. The method of claim 1, wherein the confirmation is amedium access control (MAC) control element.
 3. The method of claim 2,wherein the transmitting the confirmation is via an uplink data channel.4. The method of claim 2, wherein the confirmation comprises a firstidentifier of the third bandwidth part and a second identifier of thefourth bandwidth part.
 5. The method of claim 2, wherein the firstdownlink control information indicates an uplink grant for transmissionof one or more transport blocks via the second bandwidth part.
 6. Themethod of claim 2, wherein the first downlink control informationindicates an order for a random access procedure.
 7. The method of claim1, wherein the confirmation is an acknowledgement.
 8. The method ofclaim 7, wherein the transmitting the confirmation is via an uplinkcontrol channel.
 9. The method of claim 7, wherein the transmitting theconfirmation is via an uplink data channel.
 10. The method of claim 1,wherein the transmitting the confirmation is via an uplink controlchannel.
 11. The method of claim 1, wherein the transmitting theconfirmation is via an uplink data channel.
 12. The method of claim 1,wherein the confirmation comprises a first identifier of the thirdbandwidth part and a second identifier of the fourth bandwidth part. 13.The method of claim 1, wherein the first downlink control informationindicates an uplink grant for transmission of one or more transportblocks via the second bandwidth part.
 14. The method of claim 1, whereinthe first downlink control information indicates an order for a randomaccess procedure.
 15. The method of claim 1, wherein the second downlinkcontrol information indicates an uplink grant for transmission of one ormore transport blocks via the fourth bandwidth part.
 16. The method ofclaim 15, wherein the confirmation is a medium access control (MAC)control element.
 17. The method of claim 15, wherein the confirmation isan acknowledgement.
 18. The method of claim 1, wherein the seconddownlink control information indicates an order for a random accessprocedure.
 19. The method of claim 18, wherein the confirmation is amedium access control (MAC) control element.
 20. The method of claim 19,wherein the confirmation is an acknowledgement.